From: Stan Hoeppner <stan@hardwarefreak.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID.
Date: Sat, 01 Feb 2014 15:44:15 -0600 [thread overview]
Message-ID: <52ED6AAF.6030703@hardwarefreak.com> (raw)
In-Reply-To: <EDBD7355-F1EC-4773-9138-CA864CB2E84B@colorremedies.com>
On 2/1/2014 2:55 PM, Chris Murphy wrote:
>
> On Feb 1, 2014, at 11:47 AM, Stan Hoeppner <stan@hardwarefreak.com>
> wrote:
>
>> On 1/31/2014 12:35 AM, Chris Murphy wrote:
>>> Hopefully this is an acceptable way to avoid thread jacking, by
>>> renaming the subject…
>>>
>>> On Jan 30, 2014, at 10:58 PM, Stan Hoeppner
>>> <stan@hardwarefreak.com> wrote:
>>>>
>>>> RAID60 is a nested RAID level just like RAID10 and RAID50. It
>>>> is a stripe, or RAID0, across multiple primary array types,
>>>> RAID6 in this case. The stripe width of each 'inner' RAID6
>>>> becomes the stripe unit of the 'outer' RAID0 array:
>>>>
>>>> RAID6 geometry 128KB * 12 = 1536KB RAID0 geometry 1536KB * 3
>>>> = 4608KB
>>>
>>> My question is on this particular point. If this were hardware
>>> raid6, but I wanted to then stripe using md raid0, using the
>>> numbers above would I choose a raid0 chunk size of 1536KB? How
>>> critical is this value for, e.g. only large streaming read/write
>>> workloads? If it were smaller, say 256KB or even 32KB, would
>>> there be a significant performance consequence?
>>
>> You say 'if it were smaller...256/32KB'. What is "it"
>> referencing?
>
> it = chunk size for md raid0.
>
> So chunk size 128KB * 12 disks, hardware raid6. Chunk size 32KB [1]
> striping the raid6's with md raid0.
Frankly, I don't know whether you're pulling my chain, or really don't
understand the concept of nested striping. I'll assume the latter.
When nesting stripes, the chunk size of the outer stripe is -always-
equal to the stripe width of each inner striped array, as I clearly
demonstrated earlier:
3 RAID6 arrays
RAID6 geometry 128KB * 12 = 1536KB
RAID60 geometry 1536KB * 3 = 4608KB
mdadm allows you enough rope to hang yourself in this situation because
it doesn't know the geometry of the underlying hardware arrays, and has
no code to do sanity checking even if it did. Thus it can't save you
from yourself.
RAID HBA and SAN controller firmware simply won't allow this. They
configure the RAID60 chunk size automatically equal to the RAID6 stripe
width. If some vendor's firmware allows one to manually enter the
RAID60 chunk size with a value different from the RAID6 stripe width,
stay away from that vendor.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-02-01 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 6:35 relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID Chris Murphy
2014-02-01 18:47 ` Stan Hoeppner
2014-02-01 20:55 ` Chris Murphy
2014-02-01 21:44 ` Stan Hoeppner [this message]
2014-02-02 18:09 ` Chris Murphy
2014-02-02 21:30 ` Dave Chinner
2014-02-03 4:39 ` Stan Hoeppner
2014-02-03 5:24 ` Dave Chinner
2014-02-03 9:36 ` Stan Hoeppner
2014-02-03 21:54 ` Dave Chinner
2014-02-04 7:06 ` documentation framework [was Re: relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID.] Dave Chinner
2014-02-03 10:50 ` relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID Stan Hoeppner
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=52ED6AAF.6030703@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=lists@colorremedies.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.