From: mike dentifrice <fluor@poivron.org>
To: xfs@oss.sgi.com
Subject: sunit & swidth on RAID-1?
Date: Wed, 11 Feb 2009 16:56:38 +0100 [thread overview]
Message-ID: <20090211155638.GA3864@dentifrice> (raw)
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?
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/
--
mike dentifrice <fluor@poivron.org>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-02-11 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 15:56 mike dentifrice [this message]
2009-02-11 16:42 ` sunit & swidth on RAID-1? 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
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=20090211155638.GA3864@dentifrice \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox