MFC r306733

Add history section to fsck(8)

PR: 212472
Approved by: bcr (mentor)
Differential Revision: https://reviews.freebsd.org/D8104

MFC r266586

If called without -T or -t, fsck attempts to detect the
file system type. If this fails, fsck will fail with
"unknown file system type" message.

PR: 188214

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Add new option -c to specify alternatve location of the /etc/fstab
file.

MFC after: 1 month

Fix typos and spelling mistakes.

Note that foreground fsck should be run after a filesystem related panic.

Suggested by: Mikhail Teterin (mi@)
MFC after: 1 week

Add the '-C' "check clean" flag. If the FS is marked clean, skip file
system checking. However, if the file system is not clean, perform a
full fsck.

Reviewed by: delphij
Obtained from: Juniper Networks

Sync program's usage() with manpage's SYNOPSIS.

Fixed the misplaced $FreeBSD$.

Deal with double whitespace.

Mechanically kill hard sentence breaks.

Remove references to the '-l' option in synopsis. The rest of the
description of this option was removed in v. 1.22.

PR: docs/54880
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
Approved by: ceri (mentor)

english(4) police.

Uniformly refer to a file system as "file system".

Approved by: re

s/filesystem/file system/g as discussed on -developers

The .Nm utility

more file system > filesystem

mdoc(7) police: Fixed broken xrefs.

Remove whitespace at EOL.

mdoc(7) police: update document date, sort xrefs, fix markup.

Add support for running foreground (-F) and background (-B) checks.
Traditionally, fsck is invoked before the filesystems are mounted
and all checks are done to completion at that time. If background
checking is available, fsck is invoked twice. It is first invoked
at the traditional time, before the filesystems are mounted, with
the -F flag to do checking on all the filesystems that cannot do
background checking. It is then invoked a second time, after the
system has completed going multiuser, with the -B flag to do checking
on all the filesystems that can do background checking. Unlike
the foreground checking, the background checking is started
asynchonously so that other system activity can proceed even on
the filesystems that are being checked.

At the moment, only the fast filesystem supports background checking.
To be able to do background checking, a filesystem 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 (i.e., not listed as `noauto' in /etc/fstab).

These changes are the final piece needed to support background
filesystem checking. They will not have any effect until you update
your /etc/rc to invoke fsck in its new mode of operation. I am
still playing around with exactly what those changes should be
and should be committing them later this week.

mdoc(7) police: use .Nm instead of hardcoded name.

This change sanitizes the way fsck deals with pass numbers.

Consider this /etc/fstab:

# Device Mountpoint FStype Options Dump Pass#
/dev/ad1s1b none swap sw 0 0
/dev/ad0s1b none swap sw 0 0
/dev/ad0s1a / ufs rw 1 1
/dev/ad0s1e /home ufs rw 2 2
/dev/ad1s1e /tmp ufs rw 2 2
/dev/ad1s1f /usr ufs rw 2 2
/dev/ccd0c /syv ufs rw 2 11
proc /proc procfs rw 0 0

ccd0c is striped over /dev/ad0f and /dev/ad1g

Without this pass, fsck in preen mode will check ad0s1a first,
and then issue three processes in parallel:

One process doing ad0s1e
One process doing ad1s1e and ad1s1f
One process doing ccd0c

There is no way to tell it that ccd0c overlaps ad0 and ad1.

With the patch, it will do it this way:

pass 2:
One process doing ad0s1e
One process doing ad1s1e and ad1s1f

and when they are complete:

pass 11:
One process doing ccd0c

This is much faster and more sane.

Valid pass numbers are anything from 1 to INTMAX-1.

I retired the '-l' option which tried to allow people to do
something like this, but which didn't work and which complicated
the code an awful lot.

mdoc(7) police: split punctuation characters + misc fixes.

When trying to deduce the diskname from the name so we can run
parallel fsck's one per drive, use the shortest prefix ending in
a digit rather than the longest prefix ending in a digit.

This makes "/dev/ad0s1a" and "/dev/ad0s2a" appear to both reside
on the disk "/dev/ad0" and consequently they will be fsck'ed
sequentially rather than in parallel as now.

In general this heuristic is rather soft and errorprone. For
instance ccd may often reside on two or more physical disks. A
good solution would be to look for passes larger than 1 until no
disks are found in a particular pass, that way people could put
ccd stripes in pass 3... and have them fsck'ed sequentially.

Reviewed by: mjacob

Prepare for mdoc(7)NG.

mdoc(7) police: use the new features of the Nm macro.

mdoc(7) police: fix errors uncovered by the new feature of the Nm macro.

.. fsck wrappers aftercommit #1: I don't know how these files got lost,
but they did. Oops.