Documentation: fix description of ext4's block_validity mount option
Fix ext4 documentation according to commit 45f1a9c3f6
("ext4: enable block_validity by default")
Also fix some typos.
[ Further documentation cleanups by tytso ]
Signed-off-by: Fabian Frederick <fabf@skynet.be>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
This commit is contained in:
Родитель
ab04df7818
Коммит
9e645ab72e
|
@ -351,14 +351,13 @@ nouid32 Disables 32-bit UIDs and GIDs. This is for
|
||||||
interoperability with older kernels which only
|
interoperability with older kernels which only
|
||||||
store and expect 16-bit values.
|
store and expect 16-bit values.
|
||||||
|
|
||||||
block_validity This options allows to enables/disables the in-kernel
|
block_validity(*) These options enable or disable the in-kernel
|
||||||
noblock_validity facility for tracking filesystem metadata blocks
|
noblock_validity facility for tracking filesystem metadata blocks
|
||||||
within internal data structures. This allows multi-
|
within internal data structures. This allows multi-
|
||||||
block allocator and other routines to quickly locate
|
block allocator and other routines to notice
|
||||||
extents which might overlap with filesystem metadata
|
bugs or corrupted allocation bitmaps which cause
|
||||||
blocks. This option is intended for debugging
|
blocks to be allocated which overlap with
|
||||||
purposes and since it negatively affects the
|
filesystem metadata blocks.
|
||||||
performance, it is off by default.
|
|
||||||
|
|
||||||
dioread_lock Controls whether or not ext4 should use the DIO read
|
dioread_lock Controls whether or not ext4 should use the DIO read
|
||||||
dioread_nolock locking. If the dioread_nolock option is specified
|
dioread_nolock locking. If the dioread_nolock option is specified
|
||||||
|
|
Загрузка…
Ссылка в новой задаче