[Top] [All Lists]

Re: Question regarding XFS on LVM over hardware RAID.

To: "C. Morgan Hamill" <chamill@xxxxxxxxxxxx>, xfs <xfs@xxxxxxxxxxx>
Subject: Re: Question regarding XFS on LVM over hardware RAID.
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Wed, 29 Jan 2014 17:55:48 -0600
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1391022066-sup-5863@xxxxxxxxxxxxxxx>
References: <1391005406-sup-1881@xxxxxxxxxxxxxxx> <52E91923.4070706@xxxxxxxxxxx> <1391022066-sup-5863@xxxxxxxxxxxxxxx>
Reply-to: stan@xxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
On 1/29/2014 1:11 PM, C. Morgan Hamill wrote:
> Thanks for the quick reply.
> Excerpts from Eric Sandeen's message of 2014-01-29 10:07:15 -0500:
>> The stripe unit and width are units of geometry of the underlying
>> storage; a filesystem will span some number of stripe units, depending
>> on its size.
>> So no, the filesystem's notion of stripe geometry does not change
>> with the filesystem size.
>> You do want to make sure that stripe geometry is correct and aligned
>> from top to bottom.
> Just to make sure I've understood, for 3 14-disk RAID 6 groups striped
> together into a single RAID 60, with stripe units of 128k, split up into
> some number of LVM logical volumes, I'd create the filesystems with the
> following:
>     mkfs.xfs -d su=128k,sw=36 ...

This is not correct.  You must align to either the outer stripe or the
inner stripe when using a nested array.  In this case it appears your
inner stripe is RAID6 su 128KB * sw 12 = 1536KB.  You did not state your
outer RAID0 stripe geometry.  Which one you align to depends entirely on
your workload.

However, given that you currently intend to assemble one large array
from 3 smaller arrays, then immediately carve it into smaller pieces,
it's seems that RAID60 is probably not the correct architecture for your
workload.  RAID60 is suitable for very large streaming write/read
workloads where you are evenly distributing filesystem blocks across a
very large spindle count, with a deterministic IO pattern, and with no
RMW.  It is not very suitable for consolidation workloads, as you seem
to be describing here.

Everything starts and ends with the workload.  You always design the
storage to meet the needs of the workload, not the other way round.  You
seem to be designing your system from the storage up.  This is often a
recipe for disaster.

Please describe your workload in more detail so we can provide better,
detailed, advice.


<Prev in Thread] Current Thread [Next in Thread>