#
303975 |
|
11-Aug-2016 |
gjb |
Copy stable/11@r303970 to releng/11.0 as part of the 11.0-RELEASE cycle.
Prune svn:mergeinfo from the new branch, and rename it to RC1.
Update __FreeBSD_version.
Use the quarterly branch for the default FreeBSD.conf pkg(8) repo and the dvd1.iso packages population.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
302408 |
|
08-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
241807 |
|
21-Oct-2012 |
uqs |
Make fsck and fsck_msdosfs WARNS=6 clean
- sprinkle const - add volatile qualifier to avoid vfork clobbering
Inspired by: NetBSD PR: bin/139802 Reviewed by: ed
|
#
241806 |
|
21-Oct-2012 |
uqs |
sbin/fsck: s/perror/perr/ to avoid shadowing
- rename some other vars too - merge NetBSD license changes
Obtained from: NetBSD PR: bin/139802 Reviewed by: ed
|
#
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
|
#
123890 |
|
27-Dec-2003 |
bde |
Use __printflike() and __dead2 instead of hard-coded gccisms.
Declare perror(). We define and use a home made version of perror(3) that can't simply be removed (although it has the same interface as perror(3)) since it is very different (it prints on stdout, doesn't always print the program name, and sometimes exits). Declare it to get a reminder of this brokenness when WARNS is increased enough.
|
#
123889 |
|
27-Dec-2003 |
bde |
Garbage-collected hotroot, rawname() and unrawname() again. These became garbage when block devices were axed and were removed a few months later, but they came back (with hotroot renamed to hot + hotroot()) when the NetBSD fsck was mismerged.
|
#
123888 |
|
27-Dec-2003 |
bde |
fsck_msdosfs/main.c: - Don't use errexit() to (mis)implement usage(). Using errexit() just gave the bogus exit code 8. - Fixed 3 other style bugs in usage().
fsck/fsutil.[ch]: - Garbage-collected errexit(). It is essentially just one of NetBSD's fsck_ext2fs error printing functions, but we don't have fsck_ext2fs and the function is unsuitable for use there too (since pfatal() is also used and it printf to a different stream).
|
#
121689 |
|
29-Oct-2003 |
trhodes |
Remove redundant declaration of the perror() function, it's provided by stdio.h. Don't define DKTYPENAMES without using it.
|
#
92839 |
|
20-Mar-2002 |
imp |
o __P removed o ansi function prototypes o unifdef -D__STDC__ o __dead2 on usage prototype o remove now-bogus main prototype
|
#
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.
|
#
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.
|
#
66868 |
|
09-Oct-2000 |
adrian |
Reviewed by: rwatson, bp Approved by: rwatson Obtained from: NetBSD source tree
Second part of the fsck wrappers commit. This commit enables the new fsck code (removing the fsck/* code and replacing it with the netbsd fsck wrapper code), and enabling some FFS-based utilities to compile.
Details:
* quotacheck, fsdb required modification to use the fsck_ffs/ code rather than fsck/ . This might change later since quotacheck requires preen.c which should exist in fsck/ rather than fsck_ffs/
* src/Makefile has fsck_ffs added to it so it it built as part of the tree now
* share/doc/smm/03.fsck/ uses the SMM.doc/ stuff from fsck_ffs, not fsck.
I've tested this, and it shouldn't require any changes on your machine. The fsck wrapper reads /etc/fsck and is command-line-compatible enough to not require rc changes (well, most changes unless you want to do anything nifty by specifying the fs types explicityly, read the man page if you want further details on what it can do.)
This now allows us to support multiple filesystem types during bootup.
|