From: Eric Sandeen <sandeen@sandeen.net>
To: "C. Morgan Hamill" <chamill@wesleyan.edu>, xfs <xfs@oss.sgi.com>
Subject: Re: Question regarding XFS on LVM over hardware RAID.
Date: Wed, 29 Jan 2014 09:07:15 -0600 [thread overview]
Message-ID: <52E91923.4070706@sandeen.net> (raw)
In-Reply-To: <1391005406-sup-1881@al.wesleyan.edu>
On 1/29/14, 8:26 AM, C. Morgan Hamill wrote:
> Howdy folks,
>
> I understand that XFS have stripe unit and width configured according to
> the underlying RAID device when using LVM, but I was wondering if this
> is still the case when a given XFS-formatted logical volume takes up
> only part of the available space on the RAID. In particular, I could
> imagine that stripe width would need to be modified proportionally with
> the decrease in filesystem size. My intuition says that's false, but
> I wanted to check with folks who know for sure.
The stripe unit and width are units of geometry of the underlying
storage; a filesystem will span some number of stripe units, depending
on its size.
So no, the filesystem's notion of stripe geometry does not change
with the filesystem size.
You do want to make sure that stripe geometry is correct and aligned
from top to bottom.
I helped write up the RHEL storage admin guide, and there are some
nice words about geometry and alignment in there:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-iolimits.html
(Hopefully this is available w/o login, I think it is)
-Eric
> Thanks for any help!
> --
> Morgan Hamill
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-01-29 15:07 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 [this message]
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
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=52E91923.4070706@sandeen.net \
--to=sandeen@sandeen.net \
--cc=chamill@wesleyan.edu \
--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.