From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Optimal XFS formatting options?
Date: Fri, 20 Jan 2012 16:44:46 -0600 [thread overview]
Message-ID: <4F19EE5E.8030508@hardwarefreak.com> (raw)
In-Reply-To: <201201201652.10193@zmi.at>
On 1/20/2012 9:52 AM, Michael Monnerie wrote:
> On Dienstag, 17. Januar 2012 Stan Hoeppner wrote:
>> So to be clear, your issue with the above isn't with my partition
>> alignment math WRT the OP's P2000 array, but is with using XFS stripe
>> alignment in general, correct?
>
> Yes. I just wanted to document this as people often expand RAIDs and
> forget to apply the changes to stripe width.
>
>> There is one really simple way around this issue you describe: don't
>> add drives to an existing array. Simply create another array with
>> new disks, create a new aligned XFS on the array, and mount the
>> filesystem in an appropriate location. There is no 11th Commandment
>> stating one must have a single massive XFS atop all of one's disks.
>> ;)
>>
>> There is little to no application software today that can't be
>> configured to store its data files across multiple directories. So
>> there's no need to box oneself into the corner you describe above.
>
> It's a management burden to do that. I've learned that systems usually
> are strictly structured in their configuration, so it's often better to
> extend a RAID and to keep the config, as this is cheaper in the end. At
> least for the salaries of good admins here in Europe ;-)
If ease (or cost) of filesystem administration is of that much greater
priority than performance, then why are you using XFS in the first place
instead of EXT?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-20 22:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 17:44 Optimal XFS formatting options? MikeJeezy
2012-01-14 22:23 ` Stan Hoeppner
2012-01-16 0:27 ` MikeJeezy
2012-01-16 4:56 ` Stan Hoeppner
2012-01-16 23:11 ` Dave Chinner
2012-01-17 3:31 ` Stan Hoeppner
2012-01-17 9:19 ` Michael Monnerie
2012-01-17 11:17 ` Emmanuel Florac
2012-01-17 11:34 ` Stan Hoeppner
2012-01-20 15:52 ` Michael Monnerie
2012-01-20 22:44 ` Stan Hoeppner [this message]
2012-01-24 10:31 ` Michael Monnerie
2012-01-15 1:14 ` Peter Grandi
2012-01-20 9:03 ` Linda Walsh
2012-01-20 12:06 ` Peter Grandi
2012-01-20 15:55 ` Michael Monnerie
2012-01-23 4:21 ` Dave Chinner
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=4F19EE5E.8030508@hardwarefreak.com \
--to=stan@hardwarefreak.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