From: Ric Wheeler <rwheeler@redhat.com>
To: Mike Mestnik <cheako911@gmail.com>
Cc: linux-ext4@vger.kernel.org, "Martin K. Petersen" <mkp@mkp.net>
Subject: Re: How to use mkfs.ext4 "stride=" on RAID correctly?
Date: Fri, 15 Jan 2010 12:51:31 -0500 [thread overview]
Message-ID: <4B50AB23.8050300@redhat.com> (raw)
In-Reply-To: <fa7b26051001131658ya96c3b0ieb6010c6fba389c4@mail.gmail.com>
On 01/13/2010 07:58 PM, Mike Mestnik wrote:
> On Wed, Jan 13, 2010 at 6:13 PM, Mike Mestnik<cheako@visi.com> wrote:
>
>> 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
>>
>>
> Wait!!
> I got this all wrong, one would need all of x, n, and stride to
> successfully determine the disk used for a given stride.
>
> Seams to me mkfs is missing some parameters. What about [-g
> blocks-per-group]...
>
> http://tldp.org/HOWTO/Software-RAID-0.4x-HOWTO-8.html
>
>
Hi Mike,
Recent changes upstream export alignment and optimal IO size for you (at
least for software RAID/dm devices) and for some external arrays if the
vendor exports the information in a standard way.
Martin was the lead on that & work has been ongoing to add support up
the tool chain.
Hopefully, this will get easier to do so we all don't have to work out
the numbers each time we build on RAID :-)
Ric
>> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-01-15 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 0:12 How to use mkfs.ext4 "stride=" on RAID correctly? Mike Mestnik
2010-01-14 0:13 ` Mike Mestnik
2010-01-14 0:58 ` Mike Mestnik
2010-01-15 17:51 ` Ric Wheeler [this message]
2010-01-16 2:59 ` Mike Mestnik
2010-01-16 5:38 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B50AB23.8050300@redhat.com \
--to=rwheeler@redhat.com \
--cc=cheako911@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mkp@mkp.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).