From: Peter Rabbitson <rabbit@rabbit.us>
To: linux-raid@vger.kernel.org
Subject: Re: XFS sunit/swidth for raid10
Date: Thu, 22 Mar 2007 13:05:08 +0100 [thread overview]
Message-ID: <460270F4.1080604@rabbit.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0703220108270.13419@twinlark.arctic.org>
dean gaudet wrote:
> On Thu, 22 Mar 2007, Peter Rabbitson wrote:
>
>> Hi,
>> How does one determine the XFS sunit and swidth sizes for a software raid10
>> with 3 copies?
>
> mkfs.xfs uses the GET_ARRAY_INFO ioctl to get the data it needs from
> software raid and select an appropriate sunit/swidth...
>
> although i'm not sure i agree entirely with its choice for raid10:
So do I, especially as it makes no checks for the amount of copies (3 in
my case, not 2).
>it probably doesn't matter.
This was essentially my question. For an array -pf3 -c1024 I get swidth
= 4 * sunit = 4MiB. Is it about right and does it matter at all?
next prev parent reply other threads:[~2007-03-22 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 23:23 XFS sunit/swidth for raid10 Peter Rabbitson
2007-03-22 8:23 ` dean gaudet
2007-03-22 12:05 ` Peter Rabbitson [this message]
2007-03-23 6:48 ` dean gaudet
2007-03-23 8:20 ` Peter Rabbitson
2007-03-25 19:16 ` dean gaudet
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=460270F4.1080604@rabbit.us \
--to=rabbit@rabbit.us \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).