From: Dave Chinner <david@fromorbit.com>
To: James Woolliscroft <j_woolliscroft@hotmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Using XFS on Raid
Date: Thu, 5 Feb 2015 12:02:21 +1100 [thread overview]
Message-ID: <20150205010221.GQ4251@dastard> (raw)
In-Reply-To: <BLU436-SMTP15464F1CAAC1F46E2593ED0FB3B0@phx.gbl>
On Thu, Feb 05, 2015 at 12:23:53AM +0000, James Woolliscroft wrote:
> Hi,
>
>
>
> I am new to XFS, I have spent a significant time searching for information
> and have not found any documentation relating to the use of XFS over RAID
> with N Drives where the Stripe Unit >256K.
Use the defaults - they do the right thing.
> It appears that XFS on RHEL7 and clones is limited to a maximum Stripe Unit
> of 256KB.
That's not correct. mkfs.xfs prior to v3.2.2 (i.e the latest) throw
a warning about the default log stripe unit not being able to be set
larger than 256k, but it then sets the lsu to a default of 32k and
continues.
The current version (which I think will hit RHEL7.1) omits
the warning and just sets the lsu to 32k - defaults should just do
the right thing and not bother users who are using defaults.
Either version, however, will still result in the data stripe
unit/width is still going to be 1m/2m in your case.
> I also would like to find some information on how to correctly interpret the
> statistics output when formatting a volume with XFS, particularly as the
> process may use other settings which may require further investigation?
They are a reflection of the command line parameters, or if not
specified, the default CLI values. So, read the mkfs.xfs man page as
it explains what everything means.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-02-05 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 0:23 Using XFS on Raid James Woolliscroft
2015-02-05 1:02 ` Dave Chinner [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=20150205010221.GQ4251@dastard \
--to=david@fromorbit.com \
--cc=j_woolliscroft@hotmail.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