public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: xfs partition layout  and using xfs_growfs
Date: Sun, 20 Jun 2010 21:35:13 -0700	[thread overview]
Message-ID: <4C1EEC01.9090509@tlinx.org> (raw)


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?

Would the final file systems look pretty much the same and have roughly the
same performance characteristics?  Assume, for sake of argument, that the
file system was grown before space got tight enough to cause any severe 
large file fragmentation.  

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?

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

Thanks,
Linda

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

             reply	other threads:[~2010-06-21  4:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21  4:35 Linda A. Walsh [this message]
2010-06-21  5:53 ` xfs partition layout and using xfs_growfs Dave Chinner

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=4C1EEC01.9090509@tlinx.org \
    --to=xfs@tlinx.org \
    --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