Update man pages to include ext4 in the synposis, instead of just "ext2/ext3"

[tools/e2fsprogs.git] / misc / badblocks.8.in

diff --git a/misc/badblocks.8.in b/misc/badblocks.8.in
index b83b598..5a10f8a 100644 (file)
--- a/misc/badblocks.8.in
+++ b/misc/badblocks.8.in
@@ -20,6 +20,10 @@ badblocks \- search a device for bad blocks
 .I max_bad_blocks
 ]
 [
+.B \-d
+.I read_delay_factor
+]
+[
 .B \-i
 .I input_file
 ]
@@ -39,7 +43,7 @@ badblocks \- search a device for bad blocks
 [
 .I last-block
 ] [
-.I start-block 
+.I first-block 
 ]
 .SH DESCRIPTION
 .B badblocks
@@ -50,7 +54,7 @@ is the special file corresponding to the device (e.g
 .I last-block
 is the last block to be checked; if it is not specified, the last block
 on the device is used as a default.
-.I start-block
+.I first-block
 is an optional parameter specifying the starting block number
 for the test, which allows the testing to start in the middle of the
 disk.  If it is not specified the first block on the disk is used as a default.
@@ -90,6 +94,14 @@ Specify a maximum number of bad blocks before aborting the test.  The
 default is 0, meaning the test will continue until the end of the test
 range is reached.
 .TP
+.BI \-d " read delay factor"
+This parameter, if passed and non-zero, will cause bad blocks to sleep
+between reads if there were no errors encountered in the read
+operation; the delay will be calculated as a percentage of the time it
+took for the read operation to be performed. In other words, a value of 
+100 will cause each read to be delayed by the amount the previous read
+took, and a value of 200 by twice the amount.
+.TP
 .B \-f
 Normally, badblocks will refuse to do a read/write or a non-destructive
 test on a device which is mounted, since either can cause the system to