NAME

fsck, dfsck − file system consistency check and interactive repair

SYNOPSIS

/etc/fsck [−y ] [  −n ] [  −sX ] [  −SX ] [  −bnumbers ] [  −t file ]

[  −q ] [  −D ] [  −f ] [ file-system ... ]

/etc/dfsck [ options1 ] filsys1 ... − [ options2 ] filsys2 ...

DESCRIPTION

Fsck

fsck audits and interactively repairs inconsistent conditions for UNIX file systems.  Bell file systems and Extent file systems are both supported (see fs(4)). If the file system is consistent then the number of files, number of blocks used, and number of blocks free are reported. If the file system is inconsistent the operator is prompted for a response before each correction is attempted. Most corrective actions will result in some loss of data. To determine the amount and severity of data lost, examine the diagnostic output. The default action for each consistency correction is to wait for the operator to respond yes or no. If the operator does not have write permission, fsck will default to a −n action. 

fsck has more consistency checks than its predecessors check, dcheck, fcheck, and icheck combined. 

The following options are interpreted by fsck.

−y Assume a yes response to all questions asked by fsck.

−n Assume a no response to all questions asked by fsck; do not open the file system for writing.

−sX Ignore the actual free list and (unconditionally) reconstruct a new one by rewriting the super-block of the file system.  The file system should be unmounted doing this.  If unmounting the file system is not possible, be sure that the system is quiescent and that you reboot it immediately afterwards.  This precaution is necessary so that the old, bad, in-core copy of the superblock will not continue to be used, or written on the file system. 

The −sX option allows for creating an optimal free-list organization.  The following forms of X are supported for the following devices:

−s3 (RP03)
−s4 (RP04, RP05, RP06)
−sBlocks-per-cylinder:Blocks-to-skip (for anything else)

If X is not given, the values used when the file system was created are used.  If these values were not specified, then the value 400:7 is used.  The X parameter is meaningful only for Bell file systems.  It is ignored for Extent file systems. 

−SX Conditionally reconstruct the free list. This option is like −sX above except that the free list is rebuilt only if there were no discrepancies discovered in the file system. Using −S will force a no response to all questions asked by fsck. This option is useful for forcing free list reorganization on uncontaminated file systems.

−b Report files using any of the given physical block numbers. 

−t If fsck cannot obtain enough memory to keep its tables, it uses a scratch file. If the −t option is specified, the file named in the next argument is used as the scratch file. Without the −t flag, fsck will prompt the operator for the name of the scratch file. The file chosen should not be on the file system being checked, and if it is not a special file or did not already exist, it is removed when fsck completes. 

−q Quiet fsck. Do not print size-check messages in Phase 1.  Unreferenced fifos will silently be removed.  If fsck requires it, counts in the superblock will be automatically fixed and the free list salvaged. 

−D Directories are checked for bad blocks.  Useful after the system crashes. 

−f Fast check.  Check block and sizes (Phase 1) and check the free list (Phase 5).  If it is necessary, the free list will be reconstructed (Phase 6). 

If no file-systems are specified, fsck will read a list of default file systems from the file /etc/checklist.

Inconsistencies checked are as follows:

1.  Blocks claimed by more than one inode or the free list. 

2.  Blocks claimed by an inode or the free list outside the range of the file system. 

3.  Incorrect link counts. 

4.  Size checks:

Incorrect number of blocks. 
Directory size not 16-byte aligned.

5.  Bad inode format. 

6.  Blocks not accounted for anywhere. 

7.  Directory checks:

File pointing to unallocated inode. 
Inode number out of range.

8.  Super block checks:

More than 65536 inodes. 
More blocks for inodes than there are in the file system.

9.  Bad free block list format. 

10.  Total free block and/or free inode count incorrect. 

Nonempty orphaned files and directories (allocated but unreferenced) are, with the operator’s concurrence, reconnected by placing them in the lost+found directory.  The user will be notified whether or not the file or directory is empty.  If it is empty, fsck will silently remove them.  fsck will force the reconnection of nonempty directories.  The name assigned is the inode number.  The only restriction is that the directory lost+found must preexist in the root of the file system being checked and must have empty slots in which entries can be made.  This is accomplished by making lost+found, copying a number of files to the directory, and then removing them (before fsck is executed). A utility, mklost+foun(1M), is provided to do this.

Checking the raw device is almost always faster and should be used with everything but the root file system.  Do not check the raw device if it is mounted. 

Dfsck

dfsck allows two file system checks on two different drives simultaneously.  options1 and options2 are used to pass options to fsck for the two sets of file systems.  A − is the separator between the file system groups. 

The dfsck program permits an operator to interact with two fsck(1M) programs at once. To aid in this, dfsck will print the file system name for each message to the operator.  When answering a question from dfsck, the operator must prefix the response with a 1 or a 2 (indicating that the answer refers to the first or second file system group). 

Do not use dfsck to check the root file system (because pipes are created). 

EXAMPLES

/etc/fsck −q /dev/md0a /dev/rmd0c

checks the consistency of a IRIS 1400 or 2400 workstation with a single disk. 

/etc/fsck −q /dev/md0a /dev/rmd0c /dev/rmd1[ac]

checks the consistency of a IRIS 1400 or 2400 workstation with two disks. 

FILES

/etc/fsck.bell
/etc/fsck.efs
/etc/checklistdefault list of file systems to check. 

SEE ALSO

clri(1M), mklost+foun(1M), ncheck(1M), checklist(4), fs(4), crash(8)

“fsck”, IRIS Workstation Guide, Series 2000 , Appendix A. 

BUGS

Inode numbers for .  and .. in each directory should be checked for validity. 

DIAGNOSTICS

The diagnostics produced by fsck are intended to be self-explanatory. 
 

Version 2.4  —  May 08, 1986