summaryrefslogtreecommitdiffstats
path: root/sbin/fsck_ffs/fsck_ffs.8
Commit message (Collapse)AuthorAgeFilesLines
* MFC r313745:garga2017-02-211-41/+43
| | | | | | | | | | | | | * Add missing parameters to usage() * Add missing parameters to manpage synopsis * Add missing description of -d flag * Sort flags descriptions Reviewed by: allanjude, kib Approved by: allanjude MFC after: 1 week Sponsored by: Rubicon Communications (Netgate) Differential Revision: https://reviews.freebsd.org/D9152
* MFC r306734:sevan2016-10-161-4/+15
| | | | | | | | | Add history section to fsck_ffs(8) Move sentence to a new line as advised by igor. PR: 212474 Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8104
* Add the -R option to allow fsck_ffs to restart itself when too many criticalscottl2013-12-301-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | errors have been detected in a particular run. Clean up the global state variables so that a restart can happen correctly. Separate the global variables in fsck_ffs and fsdb to their own file. This fixes header sharing with fscd. Correctly initialize, static-ize, and remove global variables as needed in dir.c. This fixes a problem with lost+found directories that was causing a segfault. Correctly initialize, static-ize, and remove global variables as needed in suj.c. Initialize the suj globals before allocating the disk object, not after. Also ensure that 'preen' mode doesn't conflict with 'restart' mode Submitted by: scottl, max Reviewed by: max, mckusick (earlier version) Obtained from: Netflix MFC after: 3 days
* Document the -S flag to fsck_ffsscottl2013-07-311-1/+6
| | | | Obtained from: Netflix
* Add a -Z option which zeroes unused blocks. It can be combined with -E,des2013-04-291-1/+10
| | | | | | | in which case unused blocks are first zeroed and then erased. Reviewed by: mckusick MFC after: 3 weeks
* Be more helpful about alternate superblocks.trasz2012-02-101-1/+6
|
* Add an -E option to mirror newfs's. The idea is that if you have a systemdes2011-04-291-2/+20
| | | | | | | | | | | | | | | | | | | that was built before ffs grew support for TRIM, your filesystem will have plenty of free blocks that the flash chip doesn't know are free, so it can't take advantage of them for wear leveling. Once you've upgraded your kernel, you enable TRIM on the filesystem (tunefs -t enable), then run fsck_ffs -E on it before mounting it. I tested this patch by half-filling an mdconfig'ed filesystem image, running fsck_ffs -E on it, then verifying that the contents were not damaged by comparing them to a pristine copy using rsync's checksum functionality. There is no reliable way to test it on real hardware. Many thanks to mckusick@, who provided the tricky parts of this patch and reviewed the final version. Reviewed by: mckusick@ MFC after: 3 weeks
* Fix boo-boo in previous commit.des2011-04-271-7/+7
| | | | MFC after: 3 weeks
* Alphabetize the options. No date bump since no actual change to the text.des2011-04-271-4/+4
| | | | MFC after: 3 weeks
* Fix typos, spelling, formatting and mdoc mistakes found by Nobuyuki whilejoel2010-08-161-1/+1
| | | | | | translating these manual pages. Minor corrections by me. Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp>
* Fix typos and spelling mistakes.joel2010-08-061-1/+1
|
* Note that foreground fsck should be run after a filesystem related panic.mckusick2010-07-231-0/+9
| | | | | Suggested by: Mikhail Teterin (mi@) MFC after: 1 week
* Update the actions previously attempted by the -D option to make themmckusick2009-02-041-17/+10
| | | | | | | | | | | | | | | | | | robust. With these changes fsck is now able to detect and reliably rebuild corrupted cylinder group maps. The -D option is no longer necessary as it has been replaced by a prompt asking whether the corrupted cylinder group should be rebuilt and doing so when requested. These actions are only offered and taken when running fsck in manual mode. Corrupted cylinder groups found during preen mode cause the fsck to fail. Add the -r option to free up excess unused inodes. Decreasing the number of preallocated inodes reduces the running time of future runs of fsck and frees up space that can allocated to files. The -r option is ignored when running in preen mode. Reviewed by: Xin LI <delphij@> Sponsored by: Rsync.net
* Add the '-C' "check clean" flag. If the FS is marked clean, skip fileobrien2009-01-301-4/+12
| | | | | | | | system checking. However, if the file system is not clean, perform a full fsck. Reviewed by: delphij Obtained from: Juniper Networks
* Rename option 'C' to 'D' (damaged) in order to avoid a conflict with upcomingdelphij2009-01-201-22/+22
| | | | | | | Juniper 'C' (clean) flag. Requested by: obrien MFC after: 1 week
* Fix typo.delphij2009-01-121-1/+1
| | | | | Submitted by: Ben Kaduk <minimarmot gmail com> MFC after: 3 days
* Document the -F 's return statement.remko2008-09-171-0/+6
| | | | | | | | | | If the application returns succesfully the return code is 7 (which means the filesystem is clean). PR: 127432 Submitted by: edwin MFC after: 3 days
* Add a new flag, '-C' which enables a special mode that is intended fordelphij2008-04-101-2/+22
| | | | | | | | | | catastrophic recovery. Currently, this mode only validates whether a cylindergroup has good signature data, and prompts the user to decide whether to clear it as a whole. This mode is useful when there is data damage on a disk and you are working on copy of the original disk, as fsck_ffs(8) tends to abnormally exit in such case, as a last resort to recover data from the disk.
* Mention the default location of alternative super block on adelphij2005-09-201-2/+2
| | | | | | | | UFS2 file system, in fsck_ffs(8). Submitted by: KOMATSU Shinichiro <koma2 at lovepeers ! org> PR: docs/86362 MFC After: 3 days
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-101-1/+1
|
* Added the EXIT STATUS section where appropriate.ru2005-01-171-2/+2
|
* Mechanically kill hard sentence breaks.ru2004-07-021-2/+4
|
* Remove advertising clause from University of California Regent's license,markm2004-04-091-4/+0
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* Uniformly refer to a file system as "file system".ru2002-12-121-1/+1
| | | | Approved by: re
* Fix some 'SYNOPSIS' and 'usage' messages.trhodes2002-08-271-1/+1
|
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-211-35/+35
|
* mdoc(7) police: section 1 and 8 manpages document their exitru2001-12-041-4/+2
| | | | | codes under the DIAGNOSTICS section, not RETURN VALUES, which is for section 2, 3, and 9 manpages.
* Actually I haven't enumerated the return values yet (thats why I hadn'tobrien2001-12-041-1/+1
| | | | | committed it yet). So vague'ize the wording a little bit to make up for it.
* Default to WARNS=2.obrien2001-12-041-0/+4
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* Remove whitespace at EOL.dd2001-07-151-11/+11
|
* mdoc(7) police:ru2001-04-271-3/+3
| | | | document date updated, removed history info from the .Os call, cosmetics.
* Add support for the -F flag which determines whether a specifiedmckusick2001-04-241-54/+35
| | | | | | | | | | | | filesystem needs foreground checking (usually at boot time) or can defer to background checking (after the system is up and running). See the manual page, fsck_ffs(8), for details on the -F and -B options. These options are primarily intended for use by the fsck front end. All output is directed to stdout so that the output is coherent when redirected to a file or a pipe. Unify the code with the fsck front end that allows either a device or a mount point to be specified as the argument to be checked.
* mdoc(7) police: prepare for mdocNG.ru2001-04-161-1/+1
|
* Use ".Nm fsck_ffs", so that this turns up in whatis(1), and others.nik2001-02-121-2/+4
| | | | | | | Add .Xr to fsck. Prompted by: JM Jr's script that shows binaries with no whatis info Reviewed by: adrian
* Document fsck_ffs's new SIGINFO handler.iedowse2001-01-031-0/+12
| | | | Reviewed by: sheldonh
* Prepare for mdoc(7)NG.ru2000-12-181-4/+5
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-5/+5
|
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Cosmetic and documentation changes brought from earlier FreeBSD versions.julian1998-12-031-18/+26
| | | | (e.g. RCS Id:)
* Reviewed by: Don Lewis <Don.Lewis@tsc.tdk.com>julian1998-12-031-54/+58
| | | | | | | | | | | | Submitted by: Kirk McKusick <mckusick@McKusick.COM> Obtained from: Mckusick, BSDI and a host of others This exactly matches Kirks sources imported under the Tag MCKUSICK2. These are as supplied by kirk with one small change needed to compile under freeBSD. Some FreeBSD patches will be added back, though many have been added to Kirk's sources already.
* Correct use of .Nm. Add rcsid. Remove unused #includes. Use err(3).charnier1998-06-151-16/+16
|
* Restored lost reference to fsdb(8).bde1997-03-121-1/+2
| | | | Fixed weird quoting of $Id$.
* Merge from Lite2. Note that Lite2 has it's own filesystem clean checkpeter1997-03-111-5/+14
| | | | | skipping code that overrides ours sooner. One should be eliminated, but for now it works.
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Sort cross references.wosch1997-01-131-1/+2
|
* Fix the case where fsck would not see sparse directories and the kernel wouldguido1996-10-081-0/+2
| | | | | | | panic. If such a thing is fixed fsck needs a rerun (and bugs the user to do so). Reviewed by: Kirk McKusick
* Correct some man page cross references and some filempp1996-02-051-1/+0
| | | | locations.
* Remove reference to fsdb(8). We don't have it.phk1995-03-171-1/+0
|
* Added filesystem clean bit support. This only affects fsck during adg1994-08-201-0/+7
| | | | | | | preen (-p), and in that case the filesystem is skipped if it is clean. A new flag "-f" for 'force' has been added which basically gives back the old behavior of checking all the filesystems all the time. This very closely models the behavior of SunOS and Ultrix.
OpenPOWER on IntegriCloud