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

F.1.2 fsck_sfcfs(1M) Checks the GFS Shared File System for consistency and recovers the file system

[SYNOPSIS]

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

[DESCRIPTION]

The fsck command checks the GFS Shared File System for consistency and restores the file system.

High-speed recovery of the 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 is executed. If an update log replay cannot be executed because of a damaged update log or for some other reason, fsck executes a full file system check. To specify a file system to be checked, use a character-special device or specify a mount point for the file system that has existing entries in /etc/vfstab.

For special, specify the character-special device or the mount point where the file system has been built. A block-special device should not be specified because fsck is not executed if a block device is mounted.

Unless special is specified, fsck checks all GFS Shared File Systems using the fsck dev entry in /etc/vfstab. When the p (prin) option is specified, fsck checks GFS Shared File Systems with fsckpass being 1 or above.

If there is a serious inconsistency, the operator is prompted to reply yes or no before fsck executes recovery. If the operator does not have write permission for the file system, fsck executes the operation with the -n option (no corrections are made).

fsck executes automatic recovery for minor inconsistencies such as:

• i-node not referenced
• 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 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.

If a file system is configured with multiple partitions, specify the path name of the representative partition as a special file name.

[OPTIONS]

generic_options

The generic_options consist of the following options:

-V

Displays a command line, but does not execute the command.

-m

Executes a check, but does not make corrections.

-n|N

Automatically replies "no" to all inquiries. Does not open the file system for writing.

-y|Y

Automatically replies yes to all inquiries.

-o specific_options

Allows options specific to the GFS Shared File System to be specified. Insert a comma delimiter between options.

f

Executes a forcible check, regardless of the super block status flag.

p

Checks for non-conversational synopsis and makes corrections.

w

Checks only for write-enabled file systems.

log|elog|nolog

Specifies whether to perform an update log replay.

The default is log.

log

Executes an update log replay. Executes a full file system check if the log data is physically destroyed.

elog

Executes an update log replay. The command terminates immediately if the log data is physically destroyed without a full file system check being executed.

nolog

Executes a full file system check without executing an update log replay.

work=raw_device

The work disk at the time of fsck execution is specified. Two or more work disks can be specified for specification of work=raw_device and by enumerating by ".". A work disk can be specified to 16 partitions.

[OPERAND]

The following operand can be specified:

special

Specifies a character-special file for the representative partition of the GFS Shared File System or path name of the mount-point.

[EXAMPLES]

# fsck -F sfcfs /dev/sfdsk/gfs/rdsk/volume1
# fsck -F sfcfs -o nolog /dev/sfdsk/gfs/rdsk/volume1

[EXIT STATUS]

0

File system recovery has been completed normally, or no recovery was necessary.

1

An incorrect parameter was specified.

32

The file system is unmounted in all nodes, and a check is required (only when fsck -m is specified).

33

The file system is mounted.

34

stat(2) for the device failed.

36

The processing has terminated because a serious problem requiring operator intervention has occurred during the execution of the command with the p (prin) option specified.

37

An interrupt has occurred during command execution.

39

The processing has terminated because of an abnormal event occurring during command execution.

50

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]

mkfs_sfcfs(1M), sfcnewfs(1M).

crash(1M), fsck(1M), fstyp(1M), mkfs(1M), reboot(1M), stat(2), vfstab(4), attributes(5), and largefile(5) in the "Solaris X Reference Manual Collection."

[NOTES]

• The work disks for fsck_sfcfs must be equal to or larger than the calculated size using the following formula (a) from number of data partitions and file system size (gigabyte unit) of the GFS Shared File System.
  (a) 40MB + [number of data partitions] * 32MB + [file system size (gigabyte unit)] * 65MB
  
  However, when the calculated size using the above-mentioned formula (a) is larger than the calculated size using the following formula (b), the required size for the work disks for fsck_sfcfs is the calculated size using the formula (b).
  (b) 5632MB + [number of meta data partitions] * 1024MB
• 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.