<SYNOPSIS>
fsck -F sfcfs [ generic_options ] [ -o specific_options ] special
<DESCRIPTION>
The fsck_sfcfs command checks the GFS Shared File System for consistency and restores the system.
High-speed recovery of a GFS Shared File System can be performed by using the update log function. Specify whether to perform high-speed recovery by executing an update log replay when fsck_sfcfs is executed. If an update log replay cannot be executed because of a damaged update log or for some other reason, fsck_sfcfs executes a full file system check.
fsck_sfcfs is not executed if a device is mounted.
If there is a serious inconsistency, the operator is prompted to reply yes or no before fsck_sfcfs executes recovery. If the operator does not have write permission for the file system, fsck_sfcfs executes the operation with the -n option (no corrections are made).
fsck_sfcfs executes automatic recovery for minor inconsistencies such as:
Too many links in an i-node
An incorrect block included in a free list
A block appearing in both a free list and a file
An invalid value detected in a super block
When the inconsistency has been corrected, a message is displayed. When recovery of the file system is successful, fsck_sfcfs displays the number of files on the file system, the counts for blocks in use and free blocks, and the fragmentation rate.
A full check is executed for the following inconsistencies:
A block is acquired by multiple i-nodes or free lists.
A block is requested by an i-node or free list outside the range of the file system.
Invalid link count
Invalid directory size
i-node with invalid syntax
A block not referenced from anywhere
Directory check, a file pointing to an unallocated i-node, i-node number falling outside the range, the first two entries (. and ..) in a directory
Super block check: i-node blocks exceed the number of blocks in the file system.
A free block list with invalid syntax
An invalid total for the free block count and free i-node count
Independent files and directories (allocated, but not referenced) are placed in a lost+found directory and reunited with the operator's consent. They are assigned i-node numbers as names. If a lost+found directory does not exist, create it. If area for the lost+found directory is not sufficient, expand the directory.
<OPTIONS>
The generic-options is an option to support with fsck(1M) together.
Displays a command line, but does not execute the command.
Executes a check, but does not make corrections.
When specifying it, either of the following messages is output.
sfcfs fsck: sanity check: special okay
Abnormality was not detected in the correspondence of special.
sfcfs fsck: sanity check: special need log replay
special should execute the update log replay.
sfcfs fsck: sanity check: special needs checking
special should execute a full check of the filesystem.
The update log replay is automatically executed if necessary at the mount.
Please refer to the -o option for the update log replay by fsck_sfcfs and the method of executing a full check.
Automatically replies no to all inquiries. Does not open the file system for writing.
Automatically replies yes to all inquiries.
Allows options specific to a GFS Shared File System to be specified. Insert a comma delimiter between options.
Executes a forcible check, regardless of the super block status flag.
Checks for non-conversational syntax and makes corrections.
Checks only for write-enabled file systems.
Executes an update log replay. Executes a full file system check if the log data is physically destroyed.
Executes an update log replay. The command terminates immediately if the log data is physically destroyed without a full file system check being executed.
Executes a full file system check without executing an update log replay.
<OPERANDS>
The following operand can be specified:
Specifies the path name to a character or block special file for the representative partition of the GFS Shared File System or the path name of the mount-point.
<EXAMPLES>
# fsck -F sfcfs /dev/sfdsk/gfs01/rdsk/volume01 <Enter> # fsck -F sfcfs -o nolog /dev/sfdsk/gfs01/rdsk/volume01 <Enter> |
<EXIT STATUS>
File system recovery has been completed normally, or no recovery was necessary.
An incorrect parameter was specified.
The file system is unmounted, and an update log replay or a full check is required (only when fsck -m is specified).
The file system is mounted.
stat(2) for the device failed.
The processing has terminated because a serious problem requiring operator intervention has occurred during the execution of the command with the p (preen) option specified.
An interrupt has occurred during command execution.
A part of correction of the filesystem was not completed by the response of -n or no. Or, abnormality occurred while executing the command, and processing was ended.
Although command execution with the elog option specified was attempted, an update log replay could not be executed the update log was physically damaged.
<SEE ALSO>
reboot(1M), stat(2), vfstab(4) in the Solaris documentation.
<NOTES>
A file system can be checked only when all hosts that share the file system have started operation. The reason is that the information for these hosts is required.
