IBM Storwize V7000, Problem Determination Manual

Page: 282 / 314

Verify that the NFS mount is successful. If the problem persists, restart the NFS
service on the file module that is refusing the mount requests from that client.
2.
Verify that the NFS share mount is successful.
Working with file modules that report a stale NFS file handle
To recover from a file system state of “Stale NFS file handle” on a file module, you
must suspend, reboot, and resume the file module.
Note: If “Stale NFS file handle” was displayed after a client IP change, refer to
“Working with NFS clients that fail to mount NFS shares after a client IP change”
on page 257.
Due to errors or conditions related to this file module, the file module
disconnected itself from the shared file system with the other nodes. All of the file
descriptors opened to the file system through this file module have become
"stale"—as indicated by command output or an error message denoting a
Stale
NFS file handle
—and cannot access their corresponding files. When this occurs,
all affected file modules enter an unhealthy state, and a CIM similar to the
following is sent to the alert log:
GPFS Error - check stale file handle failed with error code 1:
see stale file handle on /ibm/gpfs0 on file module: mgmt001st001
If you receive the error above, perform the following steps:
1. Open the CLI in the active management node using root privileges and issue
/usr/sbin/exportfs -a
to flush the NFS cache in each file module. Verify that
the state of each affected file module is healthy and that no new “Stale NFS file
handle” CIMs appear in the alert log after resuming the file module. If the
problem persists, proceed through the following steps.
2.
Review the event log to identify the affected file system and all of the nodes
where the file system has a state of “Stale NFS file handle”.
3. Suspend each affected file module.
4. Reboot each affected file module.
5. Resume each affected file module.
6. Verify that the state of each affected file module is healthy and that no new
“Stale NFS file handle” CIMs appear in the alert log after resuming the file
module.
File module-related issues
This section covers the recovery procedures related to file module issues.
Restoring System x firmware (BIOS) settings
During critical repair actions such as the replacement of a system planar in an IBM
Storwize V7000 Unified file module, you might have to reset the System x
firmware.
The firmware and software code package for the Storwize V7000 Unified
microcode can automatically configure the default settings for the System x
firmware to the required Storwize V7000 Unified settings. However, to enable the
automatic configuration, you must reset the System x firmware from its current
state to the default configuration.
Use the following procedure to set the System x firmware to the default state and
start the automatic Storwize V7000 Unified configuration.
258
Storwize V7000 Unified: Problem Determination Guide Version