HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

f
fsck_vxfs(1M) fsck_vxfs(1M)
NAME
fsck - check and repair a VxFS file system
SYNOPSIS
/usr/sbin/fsck
[-F vxfs][-V][-mnNpPsyY
][-o full,nolog ][special... ]
DESCRIPTION
fsck checks VxFS file systems for consistency. Because VxFS records pending file system updates in an
intent log, fsck typically replays the intent log instead of doing a full structural file system check. You
can use options (-o full or -y
) to force a full structural file system check.
If special is not specified,
fsck
prompts you with each file system listed in /etc/fstab to determine
which file system to check, unless you specify
-y or -Y, to automatically answer yes to the prompts.
Options
-F vxfs Specify the VxFS file system type.
-m Check whether or not the file system is marked clean. This option does not validate the file
system. The file system could have been corrupted since it was marked clean (for example,
by a system crash), and if so, a mount could fail. In that case, a full
fsck would be
required to clean it. Use
fsck -n to test for file system corruption.
-n|N Assume a "no" response to all prompts by fsck; do not open the file system for writing, do
not replay the intent log. A full file system check is performed.
-p Produce messages that identify the device being checked.
-P With VxFS, -P is used by fsck by default; it does not provide any functionality.
-s Safe performance mode. To improve performance, a system wide sync(2) will not be issued.
-V Echo the completed command line, but do not execute the command. The command line is
generated by incorporating the user specified options and other information derived from
/etc/fstab . This option allows the user to verify the command line.
-y|Y Assume a "yes" response to all prompts by
fsck. Additionally, if the file system requires a
full file system check after the log replay, or if the
nolog suboption causes the log replay
to be skipped and the file system is not clean, then a full file system check is performed.
-o Specify VxFS file system specific options. These options can be a combination of the follow-
ing in a comma-separated list:
full Perform a full file system check.
nolog Do not perform log replay. This option may be used if the log area was physi-
cally damaged.
Note: Use fsck -o full,nolog on clean file systems. If fsck -o full without
nolog is run on a clean file system, it first replays the intent log. Since the
VX_FULLFSCK flag is set, an fsck does not update the inode and extent maps before per-
forming the full check, so it reports inconsistencies. Use the
-n option to verify file system
inconsistencies.
Because VxFS maintains an intent log, a complete check is generally not required; the default is to replay
the intent log only. If
fsck_vxfs detects file system damage or the log replay operation detects dam-
age, an indication that a complete check is required is placed in the super-block. In this case, if the -y
option was specified, the full check will be run after the log replay. If the -y option was not used, fsck
must be run again, with the -o full option to perform the full structural check.
A full check looks for the following inconsistencies:
• Blocks claimed by more than one inode or the free list.
• Blocks claimed by an inode outside the range of the file system.
• Incorrect link counts.
• Size checks:
− Incorrect number of blocks.
− Directory entry format.
• Bad inode format.
• Blocks not accounted for anywhere.
HP-UX 11i Version 1: September 2005 − 1 − Hewlett-Packard Company Section 1M−−263