Before You Begin - IBM Storwize V7000 Unified Problem Determination Manual

3. If the network interface is not available, check the cables and ensure that the
Recovering a GPFS file system
Use this procedure to recover a GPFS file system after a storage system failure has
been fully addressed.You should use this procedure only under the supervision of
IBM support.

Before you begin

Prerequisites:
v You are running this procedure on a file module.
v You are logged into the file module, which is the active file module, as root. See
v GPFS and CTDB must both be in a healthy state to run some of the commands
For storage system recovery, see the procedure for recovering a storage system.
About this task
This procedure provides steps to recover a GPFS file system after a failure of the
block storage system. The file volumes were offline and are now back online after
a repair or recovery action. The disks referred to in this procedure are the volumes
that are provided by the block storage system.
Note: Because no I/O can be done by GPFS, it is assumed for these procedures
that the storage unit failure caused the GPFS file system to unmount.
After satisfying the prerequisites above, take the following steps:
Procedure
1. Verify that GPFS is running on both file modules by using the lsnode -r
2. In the lsnode -r command output, verify that the CTDB status is also active.
3. With GPFS functioning normally on both file modules, ensure that all disks in
4. Issue the chkfs file_system_name -v | tee /ftdc/chkfs_fs_name.log1
cables are plugged in. For instance, if you have no machine connectivity
between file modules and switches, check the external Ethernet cabling. If all
cables are correctly connected, check intranet and external Internet availability.
If none of these checks indicate a problem, contact the next level of support.
"Accessing a file module as root" on page 261.
that follow.
command.
The column GPFS status shows active.
If the CTDB status shows the value unhealthy, see "Checking CTDB health" on
page 153 for steps to resolve the CTDB status.
the file system are available by running the lsdisk -r command. The
Availability column shows Up.
command to capture the output to a file.
Review the output file for errors and save it for IBM support to investigate any
problems.
If the file contains a TSM ERROR message, perform the following steps:
a. Issue the stopbackup -d file_system_name command and the stoprestore -d
file_system_name command to stop any backup or restore operation.
b. Validate that no error occurred while stopping any Tivoli Storage Manager
service.
161
Chapter 4. File module