From: Richard Scobie <richard@sauce.co.nz>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: XFS over LVM over md RAID
Date: Sat, 11 Sep 2010 09:42:02 +1200 [thread overview]
Message-ID: <4C8AA62A.9020704@sauce.co.nz> (raw)
In-Reply-To: <4C8A3F8F.4000704@sandeen.net>
Eric Sandeen wrote:
> yup F11 doesn't have all the nice blkid topology bits; F11 still has
> libblkid in e2fsprogs, from before it was liberated to util-linux-ng.
>
> (I wonder if we shouldn't just convert xfsprogs over to use the ioctls...)
Thanks both for your help. For various reasons, I'll just rely on using
the non-topology aware version.
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?
I am thinking that XFS allocates ag's across all the space and that it
will only be writing to any one array at a time, or would there be more
configured if mkfs.xfs were aware that it was being created on say, 2 x
16 RAID6 arrays?
This is based on backing up the first array prior to expansion, adding
the second and mkfs.xfs, as I imagine just expanding the fs over the
second would result in non optimal performance.
Regards,
Richard
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-10 21:41 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 [this message]
2010-09-10 22:19 ` Stan Hoeppner
-- 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=4C8AA62A.9020704@sauce.co.nz \
--to=richard@sauce.co.nz \
--cc=sandeen@sandeen.net \
--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