PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)

B.1.4 fsck_sfxfs(1M) - Checks and repairs the GFS Local File System

[SYNOPSIS]

fsck -F sfxfs [ generic_options ] [ -o specific_options ] [ special ... ]

[DESCRIPTION]

fsck audits and repairs inconsistent GFS Local File System conditions.

The GFS Local File System can be recovered at high speed with the update log function. fsck specifies whether to execute high-speed recovery by update log replay. If the update log replay cannot be performed because of a damaged update log, the fsck performs a complete check of the file system. Specify the file system that is to be checked with the character special device or the mounting point of that file system that contains the entries for /etc/vfstab.

Specify the parameter special for the character special device in which the file system has been set up or with the mounting point. A block special device should not be specified here. The fsck is not executed when the block device is mounted.

If no special device is specified fsck checks all GFS Local File Systems that contain fsckdev entries in /etc/vfstab. If the p (preen) option is specified, fsck checks the GFS Local File Systems with fsckpass 1 or more.

If a fatal error is found, fsck prompts the operator for confirmation before correcting the error. If the operator is not authorized to write to a file system, fsck operates with the -n option (no correction).

fsck automatically corrects the following minor errors:

• Some i-nodes are not referenced.
• An i-node contains too many links.
• The free list contains an incorrect block.
• A block is listed both as "free" and as a file.
• A superblock contains an invalid value.

Whenever one of these errors is corrected, a corresponding message is displayed.

When a file system was corrected successfully, the fsck displays the following items:

• Number of files on the file system
• Number of used and free blocks
• Percentage of fragmentation

A full check is executed for the following inconsistencies:

• A block was acquired by two or more i-nodes or free lists
• A block was requested by i-nodes outside the file system or the free list
• Invalid link count
• Invalid directory size
• i-nodes with an invalid format
• Non-referenced blocks
• Directory check: Files that refer to unallocated i-nodes, i-node numbers that exceed the range, directory names that start with "." or ".." .
• Superblock check: Number of i-nodes exceeds the number of file system blocks
• Free block list contains an invalid format
• Incorrect total number of free blocks or free i-nodes

Disconnected files and directories (that were allocated but not referenced) are placed and re-linked in the lost+found directory after confirmation by the operator. i-node numbers are assigned as name for these files. If the lost+found directory does not exist, it is newly created. Should this directory become insufficient, it is extended.

When a file system is configured with two or more partitions, specify the special file name under the path name for the representative partition.

[OPTIONS]

-V

This option displays the command line, but does not execute the command.

-m

This options checks the file system, but does not correct any errors.

-n|N

This option answers no to all inquiries. It does not open the file system in write mode.

-y|Y

This option answers yes to all inquiries.

-o

This option specifies local options for the GFS Local File System. Delimit these options by comma ",".

f

This option forcibly checks the file system, regardless of the superblock flag status.

p

This option checks and corrects the file system in non-conversational mode.

w

This option checks only write-enabled file systems.

log|elog|nolog

This option specifies whether to perform update log replay.

The default value is log.

log

This option performs update log replay. If log data is physically damaged, the entire file system is checked.

elog

This option performs update log replay. If log data is physically damaged, the command ends immediately, without checking and correcting the file system.

nolog

This option checks the entire file system without performing update log replay.

[EXAMPLES]

# fsck -F sfxfs /dev/sfdsk/gfs/rdsk/vol0301

# fsck -F sfxfs -o nolog /dev/sfdsk/gfs/rdsk/vol0301

[EXIT STATUS]

0 File system correction ended normally or no correction was required.

1 The specified parameter is incorrect.

32 File system mounting was canceled and a check is required. (for fsck -m only)

33 The file system is mounted.

34 stat(2) for a device failed.

36 Processing ended because an important problem, which requires operator intervention, occurred during execution of the p (preen) option.

37 An interrupt occurred during command execution.

39 An irregularity occurred during command execution and processing ended.

50 Update log replay could not executed, since an update log was damaged physically during execution of the elog option.

[SEE ALSO]

mkfs_sfxfs(1M), mount_sfxfs(1M), sfxnewfs(1M), fs_sfxfs(4)

clri(1M), crash(1M), fsck(1M), fsirand(1M), fstyp(1M), mkfs(1M), mountall(1M), reboot(1M), vfstab(4), attributes(5), largefile(5).