From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: "C. Morgan Hamill" <chamill@wesleyan.edu>, xfs <xfs@oss.sgi.com>
Subject: Re: Question regarding XFS on LVM over hardware RAID.
Date: Mon, 3 Feb 2014 08:21:52 +1100 [thread overview]
Message-ID: <20140202212152.GP2212@dastard> (raw)
In-Reply-To: <52ED61C9.8060504@hardwarefreak.com>
On Sat, Feb 01, 2014 at 03:06:17PM -0600, Stan Hoeppner wrote:
> On 1/31/2014 3:14 PM, C. Morgan Hamill wrote:
> > So, basically, --dataalignment is my friend during pvcreate and
> > lvcreate.
>
> If the logical sector size reported by your RAID controller is 512
> bytes, then "--dataalignment=9216s" should start your data section on a
> RAID60 stripe boundary after the metadata section.
>
> Tthe PhysicalExtentSize should probably also match the 4608KB stripe
> width, but this is apparently not possible. PhysicalExtentSize must be
> a power of 2 value. I don't know if or how this will affect XFS aligned
> write out. You'll need to consult with someone more knowledgeable of LVM.
You can't do single IOs of that size, anyway, so this is where the
BBWC on the raid controller does it's magic and caches sequntial IOs
until it has full stripe writes cached....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-02-02 21:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 14:26 Question regarding XFS on LVM over hardware RAID C. Morgan Hamill
2014-01-29 15:07 ` Eric Sandeen
2014-01-29 19:11 ` C. Morgan Hamill
2014-01-29 23:55 ` Stan Hoeppner
2014-01-30 14:28 ` C. Morgan Hamill
2014-01-30 20:28 ` Dave Chinner
2014-01-31 5:58 ` Stan Hoeppner
2014-01-31 21:14 ` C. Morgan Hamill
2014-02-01 21:06 ` Stan Hoeppner
2014-02-02 21:21 ` Dave Chinner [this message]
2014-02-03 16:12 ` C. Morgan Hamill
2014-02-03 21:41 ` Dave Chinner
2014-02-04 8:00 ` Stan Hoeppner
2014-02-18 19:44 ` C. Morgan Hamill
2014-02-18 23:07 ` Stan Hoeppner
2014-02-20 18:31 ` C. Morgan Hamill
2014-02-21 3:33 ` Stan Hoeppner
2014-02-21 8:57 ` Emmanuel Florac
2014-02-22 2:21 ` Stan Hoeppner
2014-02-25 17:04 ` C. Morgan Hamill
2014-02-25 17:17 ` Emmanuel Florac
2014-02-25 20:08 ` Stan Hoeppner
2014-02-26 14:19 ` C. Morgan Hamill
2014-02-26 17:49 ` Stan Hoeppner
2014-02-21 19:17 ` C. Morgan Hamill
2014-02-03 16:07 ` C. Morgan Hamill
2014-01-29 22:40 ` Stan Hoeppner
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=20140202212152.GP2212@dastard \
--to=david@fromorbit.com \
--cc=chamill@wesleyan.edu \
--cc=stan@hardwarefreak.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 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.