From: Theodore Ts'o Date: Fri, 9 Dec 2005 23:18:06 +0000 (-0500) Subject: Clarify the e2fsck man page regarding the -c option X-Git-Tag: E2FSPROGS-1.39-WIP-1210~12 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=bba44f956e4ddb81dbc444d1f973603a69d2d3fa;p=tools%2Fe2fsprogs.git Clarify the e2fsck man page regarding the -c option A user was confused about whether or not e2fsck -c performed a destructive test on the filesystem, since it stated that -cc resulted in a non-destructive read/write test. Clarify that -c does a read/only test. Signed-off-by: "Theodore Ts'o" --- diff --git a/e2fsck/ChangeLog b/e2fsck/ChangeLog index 5ee9390..be26eb2 100644 --- a/e2fsck/ChangeLog +++ b/e2fsck/ChangeLog @@ -1,5 +1,8 @@ 2005-12-09 Theodore Ts'o + * e2fsck.8.in: Clarify that e2fsck -c does a read-only scan of the + device. + * unix.c (PRS): Fix typo in error message; thanks to Solar Designer for pointing out the missing preposition. (check_mount): Don't let the user run e2fsck -ccn on the diff --git a/e2fsck/e2fsck.8.in b/e2fsck/e2fsck.8.in index 40a9358..496d2d5 100644 --- a/e2fsck/e2fsck.8.in +++ b/e2fsck/e2fsck.8.in @@ -123,11 +123,12 @@ will terminate with a fatal error. .B \-c This option causes .B e2fsck -to run the +to use .BR badblocks (8) -program to find any blocks which are bad on the filesystem, -and then marks them as bad by adding them to the bad block inode. -If this option is specified twice, then the bad block scan will be done +program to do a read-only scan of the device in order to find any bad +blocks. If any bad blocks are found, they are added to the bad block +inode to prevent them from being allocated to a file or directory. If +this option is specified twice, then the bad block scan will be done using a non-destructive read-write test. .TP .BI \-C " fd"