HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)
f
fsck_vxfs(1M) fsck_vxfs(1M)
• Directory checks:
− File pointing to unallocated inode.
− Inode number out of range.
− Linkage to parent directory.
− Hash chain linkage.
− Free space count.
• Super-block checks:
− Checksum mismatch.
− More blocks for inodes than there are in the file system.
• Structural Files:
− Fileset headers.
− Object Location Table (OLT).
− Inode list files.
− Inode allocation summary files.
− Attribute files (including Access Control Lists).
− Attribute link counts.
• Bad free block list format.
• Total free block and/or free inode count incorrect.
Orphaned files and directories (allocated but unreferenced) are, with the user’s agreement, reconnected by
placing them in the lost+found directory. The name assigned is the inode number. The only restric-
tion is that the directory lost+found must already exist in the file system’s root directory.
OUTPUT
Structural errors discovered during a full check are displayed on standard output. Responses required dur-
ing a full check are read from standard input.
The following return codes are used for the -m option for all devices other than the one used by the root
file system:
0 The file system is unmounted and clean.
31 The open of the device file failed.
32 The file system is unmounted and needs checking.
33 The file system is mounted.
34 The stat of the device failed.
Other The state could not be determined because of an error.
The following return codes are used for the -m option for the device used by the root file system:
0 The root file system is mounted read-only and is clean, or the root file system is mounted
read/write and therefore is clean.
32 The root file system is mounted read-only and needs checking.
34 The stat of the device failed.
Other The state could not be determined because of an error.
In most cases, fsck prints the following messages:
log replay in progress
replay complete - marking super-block as CLEAN
If the file system is already clean, fsck prints the following message instead:
file system is clean - log replay is not required
If fsck prints any other messages, a full structural check is needed.
ERROR/DIAGNOSTICS
All error messages that relate to the contents of a file system produced during a log replay are displayed on
standard output. All I/O failures and exit messages are displayed on standard error output.
NOTES
Checking the raw device is almost always faster.
Section 1M−−264 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005