In the E2fsprogs 1.40.7 (February 28, 2008) release You have replaced the
single extended option "stride" with to "stride and stripe-width". Also the
manual descriptions changed from
stride=stripe-size
Configure the filesystem for a RAID array with
stripe-size filesystem blocks per
stripe.
to
stride=stride-size
Configure the filesystem for a RAID array with
stride-size filesystem blocks. This
is the number of blocks read or written to disk
before moving to next disk, which
is sometimes referred to as the chunk size.
This mostly affects placement of
filesystem metadata like bitmaps at mke2fs time
to avoid placing them on a single
disk, which can hurt the performanace. It may
also be used by block allocator.
stripe-width=stripe-width
Configure the filesystem for a RAID array with
stripe-width filesystem blocks per
stripe. This is typically be stride-size * N,
where N is the number of data-bear-
ing 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.
That's huge difference.
Now my question is if the meaning of "stride" has changed or not?
I'm asking because according to new manual page, the
http://wiki.centos.org/HowTos/Disk_Optimization "Raid Math" is totally
wrong, but it may be right for pre-1.40.7 e2fsprogs.
Nobody/Anonymous
None
None
Public
|
Date: 2009-02-02 19:12 The meaning of "stride" didn't change between e2fsprogs 1.40.6 and newer |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2009-07-14 14:01 | tytso |
| allow_comments | 1 | 2009-07-14 14:01 | tytso |
| close_date | - | 2009-07-14 14:01 | tytso |
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use