linux-ext4 - How to use mkfs.ext4 "stride=" on RAID correctly?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fa7b26051001131613jc61e20fu5e4d0ccee86d6b16@mail.gmail.com>
Date:	Wed, 13 Jan 2010 18:13:12 -0600
From:	Mike Mestnik <cheako@...i.com>
To:	linux-ext4@...r.kernel.org
Subject: How to use mkfs.ext4 "stride=" on RAID correctly?

What should this value be?  From what I gather it should be the length
of data stored on a single disk for each RAID level block.  If that's
the case how is it that two given data blocks are calculated to be on
separate drives?  It seams to me that the stripe-width is also
essential in this regard, but the man page does not reflect this.

For example let's say that stride=1, then which of the following
blocks are not on the same drive as 1: 8 9 10?
The answer is dependent on the number data disks, like so.
Where x = n - 1 or n depending on the RAID type.
if x = 2 then 9
if x = 3 then 8 and 10
if x = 5 then 8 and 9

There is no way to make this calculation with out knowing x, further
more calculating x based of of both stride and stripe-width is round
about...  Why not simply ask for x, the number of data disks and have
stripe-width be the value that is calculated, as stride might not go
into stripe-width evenly leaving you with a headache.

Did I locate a bug?

Is there a better forum for this discussion?
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html