|Main index||Section 8||日本語||Options|
The kernel takes care that only a restricted class of innocuous file system inconsistencies can happen unless hardware or software failures intervene. These are limited to the following:
|Link counts in inodes too large|
|Missing blocks in the free map|
|Blocks in the free map also in files|
|Counts in the super-block wrong|
These are the only inconsistencies that
If sent a QUIT signal, fsck_ffs will finish the file system checks, then exit with an abnormal return status that causes an automatic reboot to fail. This is useful when you want to finish the file system checks during an automatic reboot, but do not want the machine to come up multiuser after the checks complete.
If fsck_ffs receives a SIGINFO (see the "status" argument for stty(1)) signal, a line will be written to the standard output indicating the name of the device currently being checked, the current phase number and phase-specific progress information.
The following flags are interpreted by fsck_ffs:
A check is done on the specified and possibly active file system.
The set of corrections that can be done is limited to those done
when running in preen mode (see the
Use the block specified immediately after the flag as
the super block for the file system.
An alternate super block is usually located at block 32 for UFS1,
and block 160 for UFS2.
Check if file system was dismounted cleanly.
If so, skip file system checks (like "preen").
However, if the file system was not cleanly dismounted, do full checks,
was invoked without
|Convert the file system to the specified level. Note that the level of a file system can only be raised. There are currently four levels defined:|
|0||The file system is in the old (static table) format.|
|1||The file system is in the new (dynamic table) format.|
|2||The file system supports 32-bit uid's and gid's, short symbolic links are stored in the inode, and directories have an added field showing the file type.|
|3||If maxcontig is greater than one, build the free segment maps to aid in finding contiguous sets of blocks. If maxcontig is equal to one, delete any existing segment maps.|
In interactive mode, fsck_ffs will list the conversion to be made and ask whether the conversion should be done. If a negative answer is given, no further operations are done on the file system. In preen mode, the conversion is listed and done if possible without user interaction. Conversion in preen mode is best used when all the file systems are being converted at once. The format of a file system can be determined from the first line of output from dumpfs(8).
This option implies the
|Enable debugging messages.|
|Clear unallocated blocks, notifying the underlying device that they are not used and that their contents may be discarded. This is useful for filesystems which have been mounted on systems without TRIM support, or with TRIM support disabled, as well as filesystems which have been copied from one device to another.|
Determine whether the file system needs to be cleaned immediately
in foreground, or if its cleaning can be deferred to background.
To be eligible for background cleaning it must have been running
with soft updates, not have been marked as needing a foreground check,
and be mounted and writable when the background check is to be done.
If these conditions are met, then
exits with a zero exit status.
Otherwise it exits with a non-zero exit status.
If the file system is clean,
it will exit with a non-zero exit status so that the clean status
of the file system can be verified and reported during the foreground
Note that when invoked with the
|Force fsck_ffs to check 'clean' file systems when preening.|
|Use the mode specified in octal immediately after the flag as the permission bits to use when creating the lost+found directory rather than the default 1777. In particular, systems that do not wish to have lost files accessible by all users on the system should use a more restrictive set of permissions such as 700.|
|Assume a no response to all questions asked by fsck_ffs except for ‘CONTINUE?’, which is assumed to be affirmative; do not open the file system for writing.|
|Preen file systems (see above).|
|Instruct fsck_ffs to restart itself if it encounters certain errors that warrant another run. It will limit itself to a maximum of 10 restarts in a given run in order to avoid an endless loop with extremely corrupted filesystems.|
Free up excess unused inodes.
Decreasing the number of preallocated inodes reduces the
running time of future runs of
and frees up space that can allocated to files.
|Surrender on error. With this flag enabled, a hard error returned on disk i/o will cause fsck_ffs to abort instead of continuing on and possibly tripping over more i/o errors.|
|Assume a yes response to all questions asked by fsck_ffs; this should be used with great caution as this is a free license to continue after essentially unlimited trouble has been encountered.|
Inconsistencies checked are as follows:
|Directory size not a multiple of DIRBLKSIZ.|
|Partially truncated file.|
|File pointing to unallocated inode.|
|Inode number out of range.|
|Directories with unallocated blocks (holes).|
|Dot or dot-dot not the first two entries of a directory or having the wrong inode number.|
|More blocks for inodes than there are in the file system.|
|Bad free block map format.|
|Total free block and/or free inode count incorrect.|
Orphaned files and directories (allocated but unreferenced) are, with the operator's concurrence, reconnected by placing them in the lost+found directory. The name assigned is the inode number. If the lost+found directory does not exist, it is created. If there is insufficient space its size is increased.
The full foreground fsck_ffs checks for many more problems that may occur after an unrecoverable disk write error. Thus, it is recommended that you perform foreground fsck_ffs on your systems periodically and whenever you encounter unrecoverable disk write errors or file-system-related panics.
|contains default list of file systems to check.|
Specific non-zero exit status values used are:
|1||Usage error (missing or invalid command arguments).|
|3||The file system superblock cannot be read. This could indicate that the file system device does not exist or is not yet ready.|
|4||A mounted file system was modified; the system should be rebooted.|
|8||General error exit.|
|16||The file system could not be completely repaired. The file system may be able to be repaired by running fsck_ffs on the file system again.|
Fsck \- The UNIX File System Check Program,
|FSCK_FFS (8)||January 13, 2018|
|Main index||Section 8||日本語||Options|
Please direct any comments about this manual page service to Ben Bullock.
|“||There are two major products of Berkeley, CA -- LSD and UNIX. We don't believe this to be strictly by coincidence.||”|
|— Jeremy S. Anderson|