From: Dave Chinner <david@fromorbit.com>
To: Marcin Sura <mailing-lists@sura.pl>, xfs@oss.sgi.com
Subject: Re: mkfs.xfs -d su=XXX,sw=YYY and future volume resize
Date: Sat, 16 Jul 2016 09:07:25 +1000 [thread overview]
Message-ID: <20160715230725.GV1922@dastard> (raw)
In-Reply-To: <20160715094647.GD3608@redhat.com>
On Fri, Jul 15, 2016 at 11:46:47AM +0200, Carlos Maiolino wrote:
> On Thu, Jul 14, 2016 at 10:19:02PM +0200, Marcin Sura wrote:
> > Hi,
> > When I create filesystem I can specify su and sw paramteres which match
> > underlying storage device.
> > So for example, If I have raid 6 volume made of 6 + 2 disks with stripe
> > size of 256k I create xfs with:
> > mkfs.xfs -d su=256k,sw=6 <disk>
> > But what if I will extend original volume by 2 disks. sw will 8. Will
> > be there a performance panelty compared to filesystem created from
> > scratch with correct sw parameter?
> > BR
> > Marcin
>
> Complementing Dave's answer, you can also mount the filesystem with new
> alignment configuration.
>
> You can use: sunit=value and swidth=value for mounting the FS with the new
> settings. man xfs for more info.
That doesn't change the fact that everything that already existed in
the filesystem would now be misaligned and hence have performance
issues on read and/or overwrite. Only newly written data will be
aligned to the new stripe width.
Also, keep in mind that stripw width cahnges are an alignment change
you generally canot make through the mount options. Static metadata
such as allocation group headers are laid out according to the
physical geometry of the filesystem, and that cannot be changed.
hence the mount options can only change the stripe unit/width when
they don't change the alignment constraints. e.g. doubling of the
stripe width will work because the alignemtn of the stripe units is
still the same. However, changing from 6 disks to 8 won't work
because it is a different physical alignment...
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:[~2016-07-15 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 20:19 mkfs.xfs -d su=XXX,sw=YYY and future volume resize Marcin Sura
2016-07-14 23:40 ` Dave Chinner
2016-07-15 9:46 ` Carlos Maiolino
2016-07-15 23:07 ` Dave Chinner [this message]
2016-07-18 10:10 ` Carlos Maiolino
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=20160715230725.GV1922@dastard \
--to=david@fromorbit.com \
--cc=mailing-lists@sura.pl \
--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