From 2ac7f06611ea3f7b1fbbc3a778e9bcdab1649a0e Mon Sep 17 00:00:00 2001 From: Theodore Ts'o Date: Thu, 10 Jul 2008 09:40:48 -0400 Subject: [PATCH] Fix incorrect definition of stripe-width in mke2fs man page Also clarified the definition of the stride-size extended option as well. Addresses-Debian-Bug: #487849 Signed-off-by: "Theodore Ts'o" --- misc/mke2fs.8.in | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in index 8dc3b6d..dc35549 100644 --- a/misc/mke2fs.8.in +++ b/misc/mke2fs.8.in @@ -191,8 +191,9 @@ following extended options are supported: Configure the filesystem for a RAID array with .I stride-size filesystem blocks. This is the number of blocks read or written to disk -before moving to next disk. This mostly affects placement of filesystem -metadata like bitmaps at +before moving to next disk, which is sometimes referred to as the +.I chunk size. +This mostly affects placement of filesystem metadata like bitmaps at .B mke2fs time to avoid placing them on a single disk, which can hurt the performanace. It may also be used by block allocator. @@ -201,7 +202,8 @@ It may also be used by block allocator. Configure the filesystem for a RAID array with .I stripe-width filesystem blocks per stripe. This is typically be stride-size * N, where -N is the number of data disks in the RAID (e.g. RAID 5 N+1, RAID 6 N+2). +N is the number of data-bearing disks in the RAID (e.g. for RAID 5 there is one +parity disk so N will be the number of disks in the array minus 1). This allows the block allocator to prevent read-modify-write of the parity in a RAID stripe if possible when the data is written. .TP -- 1.8.3.1