IBM Storwize V7000 Unified Problem Determination Manual page 293

Procedure
To check if the file systems were automatically mounted following the recovery of
the control enclosure:
1. Log on to the management CLI with your administrator credentials. For
example:
ssh admin@<management_IP address>
2. Use the lsnode -r CLI command to check the status of CTDB and GPFS on
each file module. For example:
lsnode -r
3. Use the lsmount CLI command to check if all of your file systems that should
be mounted are mounted. For example:
[kd52v6h.ibm]$ lsmount
File system Mount status Last update
gpfs0 not mounted 10/17/12 10:44 AM
gpfs1 not mounted 10/17/12 10:44 AM
gpfs2 not mounted 10/17/12 10:44 AM
EFSSG1000I The command completed successfully.
4. If all of the required file systems are mounted on both nodes then there is no
need to continue going through this procedure because network users should
be able to access files on GPFS. Otherwise use the lsdisk CLI command to
check if all of the disks are available. For example:
[kd52v6h.ibm]$ lsdisk
Name File system Failure group Type Pool
Block properties
IFS1350385068630 gpfs0 1 metadataOnly system ready up 10/17/12 10:27 AM
IFS1350385068630,io_grp0,,easytier,6005076802AD80227800000000000000
IFS1350385068806 gpfs0 1 metadataOnly system ready up 10/17/12 10:27 AM
IFS1350385068806,io_grp0,,easytier,6005076802AD80227800000000000001
IFS1350385089739 gpfs0 2 metadataOnly system ready up 10/17/12 10:27 AM
IFS1350385089739,io_grp0,,easytier,6005076802AD80227800000000000002
IFS1350385089889 gpfs0 2 metadataOnly system ready up 10/17/12 10:27 AM
IFS1350385089889,io_grp0,,easytier,6005076802AD80227800000000000003
IFS1350385108175 gpfs0 0 dataOnly system ready
IFS1350385108175,io_grp0,,easytier,6005076802AD80227800000000000004
5. If all disks are up then you can use the mountfs CLI command to mount each
file system that is not mounted. For example
mountfs <file system name>
6. Otherwise if none of the disks are up or some of the disks are not up then use
the lsvdisk CLI command to check if all of your file volumes that should be
online are online. Note that the names of file volumes are the same as the
names of the disks. For example
[kd52v6h.ibm]$ lsvdisk
id name IO_group_id IO_group_name status mdisk_grp_id mdisk_grp_name capacity
type
FC_id FC_name RC_id RC_name vdisk_UID fc_map_count copy_count fast_write_state
0 IFS1350385068630 0 io_grp0 online 1 meta1 100.00GB striped
6005076802AD80227800000000000000 0 1 not_empty
1 IFS1350385068806 0 io_grp0 online 1 meta1 100.00GB striped
6005076802AD80227800000000000001 0 1 not_empty
2 IFS1350385089739 0 io_grp0 online 2 meta2 100.00GB striped
6005076802AD80227800000000000002 0 1 not_empty
3 IFS1350385089889 0 io_grp0 online 2 meta2 100.00GB striped
6005076802AD80227800000000000003 0 1 not_empty
4 IFS1350385108175 0 io_grp0 online 0 mdiskgrp0 341.00GB striped
6005076802AD80227800000000000004 0 1 not_empty
7. If any file volumes are offline then refer to Recovering when a file volume
does not come back online.
Status Availability Timestamp
up 10/17/12 10:27 AM
Chapter 7. Recovery procedures
273