|author||Theodore Ts'o <firstname.lastname@example.org>||2005-12-09 18:18:06 -0500|
|committer||Theodore Ts'o <email@example.com>||2005-12-09 18:18:06 -0500|
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" <firstname.lastname@example.org>
2 files changed, 8 insertions, 4 deletions
diff --git a/e2fsck/ChangeLog b/e2fsck/ChangeLog
index 5ee9390b..be26eb2d 100644
@@ -1,5 +1,8 @@
2005-12-09 Theodore Ts'o <email@example.com>
+ * e2fsck.8.in: Clarify that e2fsck -c does a read-only scan of the
* 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 40a9358a..496d2d51 100644
@@ -123,11 +123,12 @@ will terminate with a fatal error.
This option causes
-to run the
.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.
.BI \-C " fd"