Recovering From A 1001 Error Code - IBM Storwize V7000 Unified Problem Determination Manual

Decrease the File System size
If you cannot increase the storage pool capacity then contact IBM Remote Technical
Support for help with decreasing the file system size by deleting an NSD.

Recovering from a 1001 error code

A 1001 error code indicates that the Storwize V7000 control enclosure has
automatically performed a recovery. The control enclosure CLI is now restricted to
make sure that there are no more block storage configuration changes until IBM
Remote Technical Support has checked that it is safe for block storage
configuration changes to be allowed again.
About this task
The file volumes presented by the control enclosure for GPFS to use as disks for
file systems may have been offline long enough to cause the file systems to be
unmounted. The file systems will usually be automatically mounted as soon as the
file volumes come back online after the control enclosure recovery. You can
immediately remount any remaining unmounted file systems without waiting for
IBM support to tell you that it is safe for you to re-enable the control enclosure
CLI.
Note: The management GUI can become very slow when the control enclosure
CLI is restricted, so the following procedure shows how to use the management
CLI to check if the file systems are mounted. However, it is better to use the
management GUI if that is working fine.
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
2. Use the lsnode -r CLI command to check the status of CTDB and GPFS on
3. Use the lsmount CLI command to check if all of your file systems that should
4. If all of the required file systems are mounted on both nodes then there is no
284
Storwize V7000 Unified: Problem Determination Guide Version
example:
ssh admin@<management_IP address>
each file module. For example:
lsnode -r
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.
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
IFS1350385068630 gpfs0
IFS1350385068806 gpfs0
IFS1350385089739 gpfs0
IFS1350385089889 gpfs0
IFS1350385108175 gpfs0
1 metadataOnly system ready up
1 metadataOnly system ready up
2 metadataOnly system ready up
2 metadataOnly system ready up
0 dataOnly
Pool Status Availability Timestamp
system ready up
10/17/12 10:2
10/17/12 10:2
10/17/12 10:2
10/17/12 10:2
10/17/12 10:2