public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs partition layout  and using xfs_growfs
Date: Mon, 21 Jun 2010 15:53:42 +1000	[thread overview]
Message-ID: <20100621055342.GL6590@dastard> (raw)
In-Reply-To: <4C1EEC01.9090509@tlinx.org>

On Sun, Jun 20, 2010 at 09:35:13PM -0700, Linda A. Walsh wrote:
> 
> Is there any difference in a file systems layout and efficiency between
> to xfs fs's of the same size, but where one was created at size
> '100%', where the other was created at size 50%, but then grown
> iteratively to 60, 70, 80, 90 and then 100% over time as it filled?

Yes.

> Would the final file systems look pretty much the same

>From a structural perspective, it depends on the size of the AGs in
the initial filesystem.  If the filesystem was big enough to begin
with (i.e.  using maximally sized AGs at mkfs time) then growing it
will result in a layout exactly the same as if it was mkfs'd at full
size.

However, the allocation patterns will be significantly different
between the two filesystems, so there will be no similarity in data
layout between the two different filesystems.

> and have roughly the
> same performance characteristics?

See previous answer.

> Assume, for sake of argument, that the
> file system was grown before space got tight enough to cause any
> severe large file fragmentation.

See previous answer. ;)

> I've been under the impression that one gained some performance benefits if one
> laid out the whole file system at once  is that a mis-impression?

I wouldn't say you "gain performance benefits" by starting with a
larger filesystem, more that a grown filesystem has different aging
characteristics to one that has not been grown. See previous answer.
;)

> That asked/said...is there any work underway to create an xfs_shrinkfs, so
> that one could go the other way?

http://xfs.org/index.php/Shrinking_Support

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      reply	other threads:[~2010-06-21  5:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21  4:35 xfs partition layout and using xfs_growfs Linda A. Walsh
2010-06-21  5:53 ` 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=20100621055342.GL6590@dastard \
    --to=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    --cc=xfs@tlinx.org \
    /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