From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: XFS over LVM over md RAID
Date: Fri, 10 Sep 2010 17:19:54 -0500 [thread overview]
Message-ID: <4C8AAF0A.6010701@hardwarefreak.com> (raw)
In-Reply-To: <4C8AA62A.9020704@sauce.co.nz>
Richard Scobie put forth on 9/10/2010 4:42 PM:
> In the future this lv will be grown in multiples of 256K chunk, 16
> drive RAID6 arrays, so am I correct in thinking that the sunit/swidth
> parameter can stay the same as it is expanded?
What is the reasoning behind adding so many terabytes under a single
filesystem?
Do you _need_ all of it under a single mount point? If not, or even if
you do, for many reasons, it may very well be better to put a single
filesystem directly on each RAID6 array without using LVM in the middle
and simply mount each filesystem at a different point, say:
/data
/data/array1
/data/array2
/data/array3
/data/array4
This method can minimize damage and downtime when an entire array is
knocked offline. We just had a post yesterday where a SATA cable was
kicked loose and took 5 drives down of a 15 drive md RAID6 set, killing
the entire filesystem. If that OP had setup 3x5 drive arrays with 3
filesystems, the system could have continued to run in a degraded
fashion, depending on his application data layout across the
filesystems. If done properly, you lose an app or two, not all of them.
This method also eliminates xfs_growfs performance issues such as what
you're describing because you're never changing the filesystem layout
when adding new arrays to the system.
In summary, every layer of complexity added to the storage stack
increases the probability of failure. As my grandmother was fond of
saying, "Don't put all of your eggs in one basket." It was salient
advice on the farm 80 years ago, and it's salient advice today with high
technology.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-10 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 22:58 XFS over LVM over md RAID Richard Scobie
2010-09-10 0:25 ` Michael Monnerie
2010-09-10 0:52 ` Richard Scobie
2010-09-10 1:14 ` Richard Scobie
2010-09-10 1:30 ` Dave Chinner
2010-09-10 2:29 ` Richard Scobie
2010-09-10 14:24 ` Eric Sandeen
2010-09-10 21:42 ` Richard Scobie
2010-09-10 22:19 ` Stan Hoeppner [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-10 23:08 Richard Scobie
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=4C8AAF0A.6010701@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