public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: linux software raid5 on lvm: sunit/swidth required?
Date: Tue, 18 Jun 2013 02:03:13 -0500	[thread overview]
Message-ID: <51C00631.9070809@hardwarefreak.com> (raw)
In-Reply-To: <57FC0B2322184044812B39B9440D8AF662898079AA@MBX1.vi.corp>

On 6/17/2013 10:06 AM, Thomas Molszich wrote:
> Hello all,
> 
> At present, does one still need to calculate and pass the sunit/swidth to mkfs.xfs or does xfs calculate
> All this on its own?
> Xfsprogs 3.1.7, linked against libblkid, kernel 3.2.48 (Ubuntu 12.04 LTS), 6x3000GB Hitachi 4k sectors
> with 512b emulation, partitions and lvm 4k aligned already.

Your subject says Linux software RAID5, i.e. the md driver.  But you
don't mention md in your msg body, only "partitions and LVM 4K aligned
already".

If you layer LVM atop a striped md array then mkfs.xfs cannot see the
geometry of the md array.  LVM is not aware of it because LVM isn't
providing the striping function, and it does not perform "pass through"
of the md geometry.  So in this case you must manually align XFS,
assuming your workload will benefit from alignment.  It may not, in
which case using the default 4K alignment would be better.

mkfs.xfs will auto configure stripe geometry if directly targeting an md
striped array.  It will not with LVM atop the striped array.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2013-06-18  7:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 15:06 linux software raid5 on lvm: sunit/swidth required? Thomas Molszich
2013-06-17 15:18 ` Eric Sandeen
2013-06-18  7:03 ` Stan Hoeppner [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=51C00631.9070809@hardwarefreak.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox