|
|
HP-UX Reference > Ffsck_vxfs(1M)HP-UX 11i Version 2: December 2007 Update |
|
NAMEfsck_vxfs: fsck — check and repair a VxFS file system SYNOPSISfsck [-F vxfs] [-V] [-mnNpPsyY] [-pP] [-o p] [special ... ] fsck [-F vxfs] [-V] [-mnNpPsyY] [-o full,mounted,nolog] [special ... ] DESCRIPTIONfsck 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. special specifies one or more special character devices, for example, /dev/rdsk/c1t0d0. If multiple devices are specified, each device is checked in turn unless the -P option or the -o p suboption is also specified, in which case the devices are checked in parallel. 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. Optionsfsck recognizes the following options:
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 damage, 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. Operandsfsck recognizes the following operand:
The -o Specific OptionsThe -o option specifies VxFS file system specific options. These options can be a combination of the following in a comma-separated list:
Check a File SystemA full check looks for the following inconsistencies:
Lost and Found DirectoryOrphaned 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 restriction is that the directory lost+found must already exist in the file system's root directory. NotesChecking the raw device is almost always faster. Unlike 2.x and earlier releases of VxFS, a full file system check does not always perform pending extended inode operations. Some extended operations can only be processed when the file system is mounted. A file system that has been marked CLEAN can still contain extended operations. If a structural flaw is detected during the intent log replay, the full fsck flag is set on the file system without operator interaction. If fsck encounters a large file on an older OS version, the command stops without completing the file system check. RETURN VALUESStructural errors discovered during a full check are displayed on standard output. Responses required during 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:
The following return codes are used for the -m option for the device used by the root file system:
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. If the -y option is specified, fsck performs (if necessary) a full check after running the intent log replay. If the -y option is not used, fsck must be invoked with the -o full option to perform a full structural check. If -o p or -P is specified, fsck prints the following messages for a device, for example /dev/rdsk/c0t0d0: /dev/rdsk/c0t0d0:log replay in progress /dev/rdsk/c0t0d0:replay complete - marking super-block as CLEAN DIAGNOSTICSAll 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. WARNINGS-o mounted allows a full check of a mounted file system. -o mounted is only used internally as part of the primary cluster node recovery process after the primary fails. Never enter this option from the command line as it can destroy a file system if not used correctly. The -s (safe performance mode) option will be obsoleted in future releases. |
|