#
259065 |
|
07-Dec-2013 |
gjb |
- Copy stable/10 (r259064) to releng/10.0 as part of the 10.0-RELEASE cycle. - Update __FreeBSD_version [1] - Set branch name to -RC1
[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so start releng/10.0 at '100' so the branch is started with a value ending in zero.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
226711 |
|
24-Oct-2011 |
sobomax |
Add new option -c to specify alternatve location of the /etc/fstab file.
MFC after: 1 month
|
#
210933 |
|
06-Aug-2010 |
joel |
Fix typos and spelling mistakes.
|
#
210382 |
|
22-Jul-2010 |
mckusick |
Note that foreground fsck should be run after a filesystem related panic.
Suggested by: Mikhail Teterin (mi@) MFC after: 1 week
|
#
187931 |
|
30-Jan-2009 |
obrien |
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
|
#
141611 |
|
10-Feb-2005 |
ru |
Sync program's usage() with manpage's SYNOPSIS.
|
#
141580 |
|
09-Feb-2005 |
ru |
Fixed the misplaced $FreeBSD$.
|
#
131506 |
|
02-Jul-2004 |
ru |
Deal with double whitespace.
|
#
131488 |
|
02-Jul-2004 |
ru |
Mechanically kill hard sentence breaks.
|
#
118057 |
|
26-Jul-2003 |
simon |
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)
|
#
108317 |
|
27-Dec-2002 |
schweikh |
english(4) police.
|
#
107788 |
|
12-Dec-2002 |
ru |
Uniformly refer to a file system as "file system".
Approved by: re
|
#
102231 |
|
21-Aug-2002 |
trhodes |
s/filesystem/file system/g as discussed on -developers
|
#
99501 |
|
06-Jul-2002 |
charnier |
The .Nm utility
|
#
96707 |
|
16-May-2002 |
trhodes |
more file system > filesystem
|
#
82139 |
|
22-Aug-2001 |
ru |
mdoc(7) police: Fixed broken xrefs.
|
#
79754 |
|
15-Jul-2001 |
dd |
Remove whitespace at EOL.
|
#
76062 |
|
27-Apr-2001 |
ru |
mdoc(7) police: update document date, sort xrefs, fix markup.
|
#
75936 |
|
25-Apr-2001 |
mckusick |
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.
|
#
75163 |
|
04-Apr-2001 |
ru |
mdoc(7) police: use .Nm instead of hardcoded name.
|
#
75015 |
|
30-Mar-2001 |
phk |
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.
|
#
71895 |
|
01-Feb-2001 |
ru |
mdoc(7) police: split punctuation characters + misc fixes.
|
#
70415 |
|
27-Dec-2000 |
phk |
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
|
#
70152 |
|
18-Dec-2000 |
ru |
Prepare for mdoc(7)NG.
|
#
68960 |
|
20-Nov-2000 |
ru |
mdoc(7) police: use the new features of the Nm macro.
|
#
68878 |
|
18-Nov-2000 |
ru |
mdoc(7) police: fix errors uncovered by the new feature of the Nm macro.
|
#
66869 |
|
09-Oct-2000 |
adrian |
.. fsck wrappers aftercommit #1: I don't know how these files got lost, but they did. Oops.
|