Resolving Problems With Missing Mounted File Systems - IBM Storwize V7000 Unified Series Problem Determination Manual

Resolving problems with missing mounted file systems

You can resolve problems with mounted file systems that are missing on Storwize
V7000 Unified file modules.
Display the file system by using the lsfs -r command. The lsmount -r -v
command shows which file modules mount the file system. The Mounted status
means that both file modules mount the file system. All other states, Partially,
Internally, or Not mounted mean that a file system is not properly mounted.
To resolve the problem with the missing mounted file system, perform the
following procedure:
1. Log in to the Storwize V7000 Unified CLI as admin.
2. Identify on which file module the file system is missing, for example,
mgmt001st001.
3. Attempt to mount the missing file system on the file module by using the
mountfs command.
mountfs gpfs0
4. Rerun the lsmount command to verify that all file systems are now mounted on
file modules 0 and 1.
5. If the mounted file systems are not consistent across the file modules, reboot
the file module on which a file system is missing, and then rerun the lsmount
command.
Reboot the file module by using the initnode command:
initnode -r -n mgmt001st001
If they are not mounted on either file module, then reboot each file module.
6. Use the lsnode command to determine when the file modules are back up and
when GPFS and CTDB are both active.
The file systems might take several minutes to get mounted after GPFS
becomes active on both file modules. More than one reboot might be required
to bring the file system back up. Allow time between reboots because the file
system might take some time before it comes back up after a reboot.
7. Verify that the CTDB status is now shown as active on both file modules, as
described in "Checking CTDB health" on page 160.
8. If a GPFS file system fails to mount, complete the following actions:
Check the output log of the lslog command and find the latest messages
a.
for mounting the file system.
If you find input/output errors and messages about a failure to read the
super block, the problem is with the DMAPI clients of the TSM/HSM
system.
Check for disk related problems, such as errors reading from a disk or
errors showing a non-existent disk. For these errors, check that the path
to the storage system is working and, if it is, that the storage system
itself is in working order.
b. For additional information, refer to the "Diagnostics: Troubleshooting
tables" information in "Troubleshooting the System x3650" in the IBM
Storwize V7000 Unified Information Center.
c. If file systems remain unmounted, contact IBM support.
163
Chapter 4. File module