From: Eric Sandeen <sandeen@sandeen.net>
To: mike dentifrice <fluor@poivron.org>
Cc: xfs@oss.sgi.com
Subject: Re: sunit & swidth on RAID-1?
Date: Wed, 11 Feb 2009 10:46:26 -0600 [thread overview]
Message-ID: <499300E2.7000207@sandeen.net> (raw)
In-Reply-To: <20090211155638.GA3864@dentifrice>
mike dentifrice wrote:
> Hello,
>
> I would like to know if it makes any sense to specify sunit & swidth
> parameters as mount options to XFS filesystems sitting on a Linux
> software RAID-1 array, as advertised here [1] or there [2].
>
> I'm asking, because it seems that chunk_size does not matter in a RAID-1
> context, nor do stripe units; or do they?
I don't think it does matter. And for what it's worth, mkfs.xfs queries
an MD raid, but ignores raid1/10/0:
/*
* Ignore levels we don't want aligned (e.g. linear)
* and deduct disk(s) from stripe width on RAID4/5/6
*/
switch (md.level) {
case 6:
md.raid_disks--;
/* fallthrough */
case 5:
case 4:
md.raid_disks--;
/* fallthrough */
case 1:
case 0:
case 10:
break;
default:
return 0;
In general, mkfs.xfs on md should just "do the right thing"
-Eric
> Any tip would be appreciated,
>
> [1] http://www.socalsysadmin.com/2008/10/15/optimizing-xfs-on-raid-arrays/
> [2] http://feedblog.org/2008/06/18/howto-configure-raid-strides-in-xfs/
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-02-11 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 15:56 sunit & swidth on RAID-1? mike dentifrice
2009-02-11 16:42 ` Justin Piszcz
[not found] ` <20090211165316.GA4430@dentifrice>
2009-02-11 17:10 ` Justin Piszcz
2009-02-11 21:12 ` Michael Monnerie
2009-02-11 16:46 ` Eric Sandeen [this message]
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=499300E2.7000207@sandeen.net \
--to=sandeen@sandeen.net \
--cc=fluor@poivron.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.