Important: Perform this procedure against the passive management node only.
1. Verify that the node that the multipathd event occurred against is the passive
management node. If the node that experiences the multipathd problems is the
active node, then perform the management node failover procedure. See
“Performing management node role failover on a “good” system” on page 158.
2. Reboot the file module. See “Rebooting a file module” on page 51.
Diagnosing a multipath event
The multipath -ll command verifies that all storage devices are either active or
not active.
The following output shows that all storage devices are active.
[root@yourmachine.mgmt001st001 ~]# multipath -ll
array1_sas_89360007 (360001ff070e9c0000000001989360007) fm-0 IBM,2073-700
[size=3.1T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=50][active]
\_ 6:0:0:0 sdb 8:16 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 8:0:0:0 sdg 8:96 [active][ready]
array1_sas_89380009 (360001ff070e9c0000000001b89380009) fm-1 IBM,2073-700
[size=3.1T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=50][active]
\_ 6:0:0:2 sdd 8:48 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 8:0:0:2 sdi 8:128 [active][ready]
The following output shows that the storage devices are not active.
[root@kd27lf6.mgmt002st001 ~]# multipath -ll
mpathq (360050768029180b06000000000000007) dm-8 IBM,2145
size=2.5G features=’1 queue_if_no_path’ hwhandler=’0’ wp=rw
| `- 5:0:0:7 sdr 65:16 failed ready running
`- 6:0:0:7 sdi 8:128 failed ready running
mpathp (360050768029180b06000000000000005) dm-3 IBM,2145
size=2.5G features=’1 queue_if_no_path’ hwhandler=’0’ wp=rw
| `- 5:0:0:5 sdp 8:240 failed ready running
`- 6:0:0:5 sdg 8:96 failed ready running
The output [active][ready] identifies an active device. The output failed ready
running identifies a device that is not active.
Recovering from an NFSD service error
Use this procedure to recover from an NFSD service error.
This recovery procedure starts the NFSD when it is down.
1. Log in as root.
2. Issue the service nfsd start command.
3. If the problem persists, restart the node.
4. If the restart action does not resolve the issue, contact the next level of support.
Recovering from an SCM error
Use this procedure to recover from a service configuration management (SCM)
error.
Complete the following procedure if output from the lshealth -r CLI command
contains a line similar to the following:
SCM ERROR SCM system has found some errors
260 Storwize V7000 Unified: Problem Determination Guide Version
To Next Page
Loading...
Need help?
General