Resolving Problems With Missing Mounted File Systems - IBM Storwize V7000 Unified Problem Determination Manual
Hide thumbs
Also See for Storwize V7000 Unified:
- Introduction and implementation manual (670 pages) ,
- Problem determination manual (474 pages) ,
- Troubleshooting and maintenance manual (189 pages)
Table of Contents
Advertisement
2. To identify the currently created file systems on each Storwize V7000 Unified
Resolving problems with missing mounted file systems
You can resolve problems with mounted file systems that are missing on Storwize
V7000 Unified file modules.
About this task
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.
Procedure
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,
3. Mount the missing file system on the file module by using the mountfs
4. Issue the lsmount command to verify that all file systems are now mounted on
5. If the mounted file systems are not consistent across the file modules, reboot
6. Use the lsnode command to determine when the file modules are back up and
7. Verify that the CTDB status is now shown as active on both file modules, as
8. If a GPFS file system fails to mount, complete the following steps:
172
Storwize V7000 Unified: Problem Determination Guide Version
file module, log in as the root user on the active management node, then enter
the onnode -n mgmt001st001 df | grep ibm command from the CLI, as shown
in the following example:
# onnode -n mgmt001st001 df | grep ibm
/dev/gpfs1
3221225472
Repeat the command for another file module by using the onnode -n
mgmt002st001 df | grep ibm command, for example:
# onnode -n mgmt002st001 df | grep ibm
/dev/gpfs1
3221225472
mgmt001st001.
command.
mountfs gpfs0
file modules 0 and 1.
the file module on which a file system is missing, and then issue the lsmount
command.
Reboot the file module by using the management GUI.
If they are not mounted on either file module, then reboot each file module.
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.
described in "Checking CTDB health" on page 169.
a.
Check the output log of the lslog command and look for the latest
messages about mounting the file system.
4590080 3216635392
1% /ibm/gpfs1
4590080 3216635392
1% /ibm/gpfs1
Advertisement
Table of Contents
Troubleshooting
