6.1 HP IBRIX X9000 Network Storage System File System User Guide (TA768-96061, June 2012)

The ibrix_fsck command can detect and repair file system inconsistencies. 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 of the file system.
If a file system shows evidence of inconsistencies, 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 run, 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 44)), or you will be unable to mount the file system.
Analyzing the integrity of a file system on all segments
Observe the following requirements when executing ibrix_fsck:
Unmount the file system for phases 0 and 1 and mount the file system for phases 2 and 3.
Turn off automated failover by executing ibrix_host -m -U -h SERVERNAME.
Unmount all NFS clients and stop NFS on the servers.
Use the following procedure to analyze file system integrity:
Runs phase 0 in analytic mode:
ibrix_fsck -p 0 -f FSNAME [-s LVNAME] [-c]
The command can be run on the specified file system or optionally only on the specified segment
LVNAME.
Run phase 1 in analytic mode:
ibrix_fsck -p 1 -f FSNAME [-s LVNAME] [-c] [-B BLOCKSIZE] [-b
ALTSUPERBLOCK]
The command can be run on file system FSNAME or optionally only on segment LVNAME. This
phase can be run with a specified block size and an alternate superblock number. For example:
ibrix_fsck -p 1 -f ifs1 -B 4096 -b 12250
NOTE: If phase 1 is run in analytic mode on a mounted file system, false errors can be reported.
Checking and repairing file systems 43