5.6 HP StorageWorks X9000 File Serving Software User Guide (TA768-96035, June 2011)

Deleting file serving nodes and X9000 clients
Before deleting a file serving node, unmount all file systems from it and migrate any segments that
it owns to a different server. Ensure that the file serving node is not serving as a failover standby
and is not involved in network interface monitoring. To delete a file serving node, use the following
command:
<installdirectory>/bin/ibrix_server -d -h HOSTLIST
For example, to delete file serving nodes s1.hp.com and s2.hp.com:
<installdirectory>/bin/ibrix_server -d -h s1.hp.com,s2.hp.com
To delete X9000 clients, use the following command:
<installdirectory>/bin/ibrix_client -d -h HOSTLIST
Checking and repairing file systems
CAUTION: Do not run ibrix_fsck in corrective mode without the direct guidance of HP Support.
If run improperly, the command can cause data loss and file system damage.
CAUTION: Do not run e2fsck (or any other off-the-shelf fsck program) on any part of a file
system. Doing this can damage the file system.
The ibrix_fsck command can detect and repair file system inconsistencies, which are a symptom
of file system corruption. File system inconsistencies can occur for many reasons, including hardware
failure, power failure, switching off the system without proper shutdown, and failed migration.
The command runs in four phases and has two running modes: analytical and corrective. You must
run the phases in order and you must run all of them:
• Phase 0 checks host connectivity and the consistency of segment byte blocks and repairs them
in corrective mode.
• Phase 1 checks segments and repairs them in corrective mode. Results are stored locally.
• Phase 2 checks the file system and repairs it in corrective mode. Results are stored locally.
• Phase 3 moves files from lost+found on each segment to the global lost+found directory
on the root segment for the file system.
If a file system shows evidence of corruption, contact HP Support. A representative will ask you to
run ibrix_fsck in analytical mode and, based on the output, will recommend a course of action
and assist in running the command in corrective mode. HP strongly recommends that you use
corrective mode only with the direct guidance of HP Support. Corrective mode is complex and
difficult to run safely. Using it improperly can damage both data and the file system. Analytical
mode is completely safe, by contrast.
NOTE: During an ibrix_fsck job, an INFSCK flag is set on the file system to protect it. If an
error occurs during the job, you must explicitly clear the INFSCK flag (see “Clearing the INFSCK
flag on a file system” (page 35)), or you will be unable to mount the file system.
Analyzing the integrity of a file system on all segments
Use the following procedure to analyze file system integrity:
1. Turn off automated failover (see “Turning automated failover on and off” in the administration
guide for your system), unmount all NFS clients and stop NFS, and then unmount the file
system.
34 Maintaining file systems