mirror of https://github.com/vitalif/e2fsprogs
mke2fs.8, badblocks.8: fix spelling errors and other miscellaneous typos
Reported-by: Pete <pete@leptonyx.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>debian
parent
8feb6f439a
commit
a7dc56f45e
|
@ -9,21 +9,21 @@ badblocks \- search a device for bad blocks
|
|||
]
|
||||
[
|
||||
.B \-b
|
||||
.I block-size
|
||||
.I block_size
|
||||
]
|
||||
[
|
||||
.B \-c
|
||||
.I blocks_at_once
|
||||
]
|
||||
[
|
||||
.B \-e
|
||||
.I max_bad_blocks
|
||||
]
|
||||
[
|
||||
.B \-d
|
||||
.I read_delay_factor
|
||||
]
|
||||
[
|
||||
.B \-e
|
||||
.I max_bad_blocks
|
||||
]
|
||||
[
|
||||
.B \-i
|
||||
.I input_file
|
||||
]
|
||||
|
@ -41,9 +41,9 @@ badblocks \- search a device for bad blocks
|
|||
]
|
||||
.I device
|
||||
[
|
||||
.I last-block
|
||||
.I last_block
|
||||
] [
|
||||
.I first-block
|
||||
.I first_block
|
||||
]
|
||||
.SH DESCRIPTION
|
||||
.B badblocks
|
||||
|
@ -51,10 +51,10 @@ is used to search for bad blocks on a device (usually a disk partition).
|
|||
.I device
|
||||
is the special file corresponding to the device (e.g
|
||||
.IR /dev/hdc1 ).
|
||||
.I last-block
|
||||
.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 first-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.
|
||||
|
@ -83,17 +83,12 @@ and
|
|||
programs.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.BI \-b " block-size"
|
||||
.BI \-b " block_size"
|
||||
Specify the size of blocks in bytes. The default is 1024.
|
||||
.TP
|
||||
.BI \-c " number of blocks"
|
||||
is the number of blocks which are tested at a time. The default is 64.
|
||||
.TP
|
||||
.BI \-e " max bad block count"
|
||||
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
|
||||
|
@ -102,6 +97,11 @@ 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
|
||||
.BI \-e " max bad block count"
|
||||
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
|
||||
.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
|
||||
|
|
|
@ -666,12 +666,12 @@ program should be run immediately after this option is used, and there
|
|||
is no guarantee that any data will be salvageable. Due to the wide
|
||||
variety of possible options to
|
||||
.BR mke2fs
|
||||
that affect the on-disk layout, is critical to specify exactly the same
|
||||
that affect the on-disk layout, it is critical to specify exactly
|
||||
the same format options, such as blocksize, fs-type, feature flags, and
|
||||
other tunables when using this option, or the filesystem will be further
|
||||
corrupted. In some cases, such as filesystems that have been resized,
|
||||
or have had features enabled after format time, it is impossible to
|
||||
overwrite all of the superblocks corretly, and at least some filesystem
|
||||
overwrite all of the superblocks correctly, and at least some filesystem
|
||||
corruption will occur. It is best to run this on a full copy of the
|
||||
filesystem so other options can be tried if this doesn't work.
|
||||
.\" .TP
|
||||
|
|
Loading…
Reference in New Issue