HP StoreAll Storage - Manual (Page 49)

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 49) ), 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 the 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.
Run phase 2:
ibrix_fsck -p 2 -f FSNAME [-s LVNAME] [-c] [-o "options"]
The command can be run on the specified file system or optionally only on segment LVNAME. Use
-o
to specify any options.
Run phase 3:
ibrix_fsck -p 3 -f FSNAME [-c]
Clearing the INFSCK flag on a file system
To clear the INFSCK flag, use the following command:
ibrix_fsck -f FSNAME -C
Troubleshooting file systems
Segment of a file system is accidently deleted
When a segment of a file system is accidently deleted without evacuating it first, all files on that
segment are gone, including the Express Query metadata database files on that segment even
though they are unrelated to the files on that segment. You must recreate the metadata database.
To recreate the metadata database:
Troubleshooting file systems 49