From: Stan Hoeppner <stan@hardwarefreak.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs hardware RAID alignment over linear lvm
Date: Wed, 25 Sep 2013 16:48:11 -0500 [thread overview]
Message-ID: <52435A1B.8040207@hardwarefreak.com> (raw)
In-Reply-To: <2F959FD9-EF28-4495-9D0B-59B93D89C820@colorremedies.com>
On 9/25/2013 4:34 PM, Chris Murphy wrote:
>
> On Sep 25, 2013, at 3:18 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>
>> On 9/25/2013 7:56 AM, Stewart Webb wrote:
>>> Hi All,
>>
>> Hi Stewart,
>>
>>> I am trying to do the following:
>>> 3 x Hardware RAID Cards each with a raid 6 volume of 12 disks presented to
>>> the OS
>>> all raid units have a "stripe size" of 512 KB
>>
>> Just for future reference so you're using correct terminology, a value
>> of 512KB is surely your XFS su value, also called a "strip" in LSI
>> terminology, or a "chunk" in Linux software md/RAID terminology. This
>> is the amount of data written to each data spindle (excluding parity) in
>> the array.
>>
>> "Stripe size" is a synonym of XFS sw, which is su * #disks. This is the
>> amount of data written across the full RAID stripe (excluding parity).
>>
>>> so given the info on the xfs.org wiki - I sould give each filesystem a
>>> sunit of 512 KB and a swidth of 10 (because RAID 6 has 2 parity disks)
>>
>> Partially correct. If you format each /dev/[device] presented by the
>> RAID controller with an XFS filesystem, 3 filesystems total, then your
>> values above are correct. EXCEPT you must use the su/sw parameters in
>> mkfs.xfs if using BYTE values. See mkfs.xfs(8)
Small correction: su is a byte value. sw is an integer representing
the number of data spindles.
>>> all well and good
>>>
>>> But - I would like to use Linear LVM to bring all 3 cards into 1 logical
>>> volume -
>>> here is where my question crops up:
>>> Does this effect how I need to align the filesystem?
>>
>> In the case of a concatenation, which is what LVM linear is, you should
>> use an XFS alignment identical to that for a single array as above.
>
> So keeping the example, 3 arrays x 10 data disks, would this be su=512k and sw=30?
No. In this configuration, as far as XFS is concerned LVM doesn't exist
in the stack because it doesn't change the RAID geometry, so you ignore it.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-25 21:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 12:56 xfs hardware RAID alignment over linear lvm Stewart Webb
2013-09-25 21:18 ` Stan Hoeppner
2013-09-25 21:34 ` Chris Murphy
2013-09-25 21:48 ` Stan Hoeppner [this message]
2013-09-25 21:53 ` Chris Murphy
2013-09-25 21:57 ` Dave Chinner
2013-09-26 8:44 ` Stan Hoeppner
2013-09-26 8:55 ` Stewart Webb
2013-09-26 9:22 ` Stan Hoeppner
2013-09-26 9:28 ` Stewart Webb
2013-09-26 21:58 ` Dave Chinner
2013-09-27 1:10 ` Stan Hoeppner
2013-09-27 12:23 ` Stewart Webb
2013-09-27 13:09 ` Stan Hoeppner
2013-09-27 13:29 ` Stewart Webb
2013-09-28 14:54 ` Stan Hoeppner
2013-09-30 8:48 ` Stewart Webb
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=52435A1B.8040207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox