EasyManuals Logo

IBM Storwize V7000 Unified Problem Determination Guide

IBM Storwize V7000 Unified
474 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #217 background imageLoading...
Page #217 background image
v Perform a reboot of the unhealthy file module. Refer to “Resuming services
on a suspended file module” in the IBM Storwize V7000 Unified Information
Center.
v If none of the above actions resolves the problem, contact IBM Remote
Technical Support.
Checking the GPFS file system mount on each file module
Use this information to identify and resolve problems with General Parallel File
System (GPFS) file system mounts on IBM Storwize V7000 Unified file modules.
About this task
A GPFS file system that is not mounted on an Storwize V7000 Unified file module
can cause the clustered trivial database (CTDB) status to be 'UNHEALTHY'." The
GPFS file system must be mounted on both file modules in the Storwize V7000
Unified product to support dual redundancy and to allow file input/output
through all public IP addresses.
Note: You cannot change the cluster and file system configuration, when one of
the nodes hosting the GPFS primary or secondary configuration server is not
present in the cluster. You can identify the nodes hosting the primary or secondary
configuration server in the output of the lscluster CLI command. This also
applies to disk management operations such as creating or deleting a file system,
adding or removing a disk using the CLI commands such as mkfs, rmfs, chfs, and
rpldisk. It also includes the changes to the cluster configuration such as addnode
and delnode. These CLI commands report an error and fail the operations when
this condition is detected in the cluster.
Use the following procedure to get a file system that is not mounted on a file
module to be mounted. Contact IBM Remote Technical Support if this procedure
does not work.
Procedure
v To identify all of the currently created file systems on the Storwize V7000
Unified system, or on each file module, perform the procedure in “Identifying
created and mounted file system mounts.”
v To resolve problems with mounted file systems that are missing, perform the
procedure in “Resolving problems with missing mounted file systems” on page
190.
v To resolve problems with stale NFS file systems, perform the procedure in
“Resolving stale NFS file systems” on page 191.
v To resolve problems that are not covered by the information that is presented in
the previous topics, perform the procedure in “Recovering a GPFS file system”
on page 196.
Identifying created and mounted file system mounts
You can identify and resolve problems in GPFS file system mounts on the Storwize
V7000 Unified system and file modules.
Chapter 4. File module 189

Table of Contents

Other manuals for IBM Storwize V7000 Unified

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the IBM Storwize V7000 Unified and is the answer not in the manual?

IBM Storwize V7000 Unified Specifications

General IconGeneral
ModelIBM Storwize V7000 Unified
Storage TypeUnified Storage
RAID LevelsRAID 0, 1, 5, 6, 10
Form Factor2U
Drive Types SupportedSAS, SSD
Maximum Drives504
Network ProtocolsiSCSI, FC, FCoE
Drive Bays24 per enclosure
Host Interface8 Gb FC, 1 Gb/10 Gb iSCSI
File ProtocolsNFS, CIFS
Block ProtocolsiSCSI, Fibre Channel
TypeUnified Storage
Maximum Host Ports16
Operating System SupportVMware, Microsoft Windows, Linux, AIX
Data ServicesThin provisioning, replication
Power SupplyRedundant power supplies
Host Interfaces8 Gbps Fibre Channel, 10 Gbps iSCSI, 1 Gbps iSCSI

Related product manuals