Manual page for fsck(1M)
fsck - check and repair file systems
audits and interactively repairs
inconsistent file system conditions.
If the file system is inconsistent
the default action for each correction is to
wait for the user to respond
If the user does not have write
defaults to a
Some corrective actions
will result in loss of data.
The amount and severity of data loss may be determined from the
are options specified in a comma-separated
(with no intervening spaces) list of options or keyword-attribute pairs for
module of the command.
represents the block or character special
device (for example,
on which the file system resides.
In general, the character special device should be used.
will not work on a block device if it is mounted.
device is specified
checks the file systems listed in in
Those entries in
which have a character special device entry in the
field and have a non-zero numeric entry in the
field will be checked. Specifying
limits the file
systems to be checked to those of the type indicated.
is specified, but
is not, the file system type will
be determined by looking for a matching entry in
entry is found, the default local file system type specified in
will be used.
If a file system type supports parallel checking (for example,
some file systems eligible for checking may be checked in parallel.
Consult the file system-specific man page (for example,
for more information.
Specify the file system type on which to operate.
Check but do not repair. This option checks that the file system
is suitable for mounting, returning the appropriate exit status.
If the file system is
ready for mounting,
displays a message such as:
ufs fsck: sanity check: /dev/rdsk/c0t3d0s1 okay
response to all questions asked by
do not open the file system for writing.
Echo the expanded command line
but do not execute the command.
This option may be used to verify and validate the command line.
response to all questions asked by
- -o specific-options
can be any combination of the
following separated by commas (with no intervening spaces).
as the super block for the file system.
Block 32 is always one of the alternate super blocks. The location of
other super blocks may be determined by running
If the file system is in the old (static table) format,
convert it to the new (dynamic table) format.
If the file system is in the new format, convert it to
the old format provided the old format can support the
file system configuration.
In interactive mode,
will list the direction the conversion is 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 direction of 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
It should be noted that the
option is seldom used and is included
only for compatibility with pre-4.1 releases. There is no guarantee
that this option will be included in future releases.
Force checking of file systems regardless of the
state of their super block clean flag.
(``preen'') Check and fix the file system non-interactively.
Exit immediately if there is a problem requiring intervention.
This option is required to enable parallel file system checking.
Check writable file systems only.
file system is okay and does not need checking
erroneous parameters are specified
file system is unmounted and needs checking
(fsck -m only)
file system is already mounted
cannot stat device
uncorrectable errors detected - terminate normally
a signal was caught during processing
uncorrectable errors detected - terminate immediately
for root, same as
default local file system type. Default values can be set for the following flags in /etc/default/fs.
The default partition for a command if no FSType is specified.
list of default parameters for each file system
Manual pages for the
The operating system buffers file system data. Running
on a mounted file system can cause the operating system's buffers
to become out of date with respect to the disk. For this reason,
the file system should be
If this is
not possible, care should be taken that the system is quiescent and that
it is rebooted immediately after
Quite often, however, this will not be sufficient. A panic will probably
occur if running
on a file system modifies the file system.
This command may not be supported for all
Created by unroff & hp-tools.
© by Hans-Peter Bischof. All Rights Reserved (1997).
Last modified 21/April/97