Checking The Gpfs File System Mount On Each File Module; Identifying Created And Mounted File System Mounts - IBM Storwize V7000 Unified Problem Determination Manual

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 file modules in the Storwize V7000 Unified
product to support dual redundancy and to allow file input/output through all
public IP addresses. 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'."
To identify the CTDB status, see "Checking CTDB health" on page 169.
Procedure
v To identify all of the currently created file systems on the Storwize V7000
v To resolve problems with mounted file systems that are missing, perform the
v To resolve problems with stale NFS file systems, perform the procedure in
v To resolve problems that are not covered by the information presented in the

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.
Procedure
To identify and resolve problems in file system mounts, perform this procedure:
1. To identify all the currently created file systems on the Storwize V7000 Unified
# lsfs -r
EFSSG0015I Refreshing data.
Cluster Device name Quota
kd18pz5.ibm gpfs1 user;group;fileset
Replication Dmapi Block allocation type Last update
none yes scatter
EFSSG1000I The command completed successfully.
v If none of the above actions resolves the problem, contact the next level of
support.
Unified system, or on each file module, perform the procedure in "Identifying
created and mounted file system mounts."
procedure in "Resolving problems with missing mounted file systems" on page
172.
"Resolving stale NFS file systems" on page 173.
previous topics, perform the procedure in "Recovering a GPFS file system" on
page 176.
system, log in as the admin user, then enter the lsfs -r command from the
command-line interface (CLI), as shown in the following example:
Def. quota Block size Inodes
256 kB
10/3/11 2:08 PM
11373
171
Chapter 4. File module