.RI [ fd ]]
.RB [ \-t
.IR fstype ]
-.RI [ filesystem ...]
+.RI [ filesystem \&...\&]
.RB [ \-\- ]
.RI [ fs-specific-options ]
.SH DESCRIPTION
.B \-l
Lock the whole-disk device by an exclusive
.BR flock (2).
-This option can be used with one device only (this means that \fB-A\fR and
-\fB-l\fR are mutually exclusive). This option is recommended when more
+This option can be used with one device only (this means that \fB\-A\fR and
+\fB\-l\fR are mutually exclusive). This option is recommended when more
.BR fsck (8)
instances are executed in the same time. The option is ignored when used for
multiple devices or for non-rotating disks. \fBfsck\fR does not lock underlying
-devices when executed to check stacked devices (e.g. MD or DM) -- this feature is
+devices when executed to check stacked devices (e.g.\& MD or DM) \(en this feature is
not implemented yet.
.TP
.B \-r
-Report certain statistics for each fsck when it completes. These statistics
+Report certain statistics for each fsck when it completes. These statistics
include the exit status, the maximum run set size (in kilobytes), the elapsed
-all-clock time and the user and system CPU time used by the fsck run. For
+all-clock time and the user and system CPU time used by the fsck run. For
example:
/dev/sda1: status 0, rss 92828, real 4.002804, user 2.677592, sys 0.86186
multiple filesystem checks on the same physical disk.
.sp
.B fsck
-does not check stacked devices (RAIDs, dm-crypt, ...) in parallel with any other
+does not check stacked devices (RAIDs, dm-crypt, \&...\&) in parallel with any other
device. See below for FSCK_FORCE_ALL_PARALLEL setting. The /sys filesystem is
used to detemine dependencies between devices.
.sp
to automatically run filesystem checkers in parallel if it is advantageous
to do so. System administrators might choose
not to use this configuration if they need to avoid multiple filesystem
-checks running in parallel for some reason --- for example, if the
+checks running in parallel for some reason \(en for example, if the
machine in question is short on memory so that
excessive paging is a concern.
.sp
.B don't bother reporting it as a bug.
You're almost certainly doing something that you shouldn't be doing
with
-.BR fsck.
+.BR fsck .
.PP
Options to different filesystem-specific fsck's are not standardized.
If in doubt, please consult the man pages of the filesystem-specific
and
.BR fsck.cramfs (8)
do not support the
-.B -y
+.B \-y
option as of this writing.
.SH FILES
.IR /etc/fstab .
.B LIBMOUNT_DEBUG=0xffff
enables debug output.
.SH SEE ALSO
+.na
.BR fstab (5),
.BR mkfs (8),
.BR fsck.ext2 (8)
.BR fsck.xfs (8),
.BR fsck.xiafs (8),
.BR reiserfsck (8).
+.ad
.SH AUTHOR
.MT tytso@mit.edu
Theodore Ts'o