From: Dave Chinner <david@fromorbit.com>
To: Norbert Veber <nveber@pyre.virge.net>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: Small files perform much faster on newly formatted fs?
Date: Fri, 10 Jun 2011 07:17:31 +1000 [thread overview]
Message-ID: <20110609211731.GT32466@dastard> (raw)
In-Reply-To: <20110609134811.GI28625@pyre.virge.net>
On Thu, Jun 09, 2011 at 09:48:11AM -0400, Norbert Veber wrote:
> On Thu, Jun 09, 2011 at 11:29:07AM +1000, Dave Chinner wrote:
> > Those mount options are ignored if the filesystem doesn't have the
> > superblock feature bit set for aligned allocations. A filesystem
> > with 0/0 for sunit/swidth does not have the superblock bit set....
>
> Oh man! I thought I saw some improvement with iometer benchmarks before
> and after the mount options, but I dont see any significant difference
> while timing the untar and rm -rf I've been doing.
>
> All the documentation I came across including the man page and XFS faq
> entry imply that the mount options can be used to perform alignment..
The mount options are only there to cahnge the alignment that
already exists, and there are significant limitations on those
changes.
You can't just apply alignment to a filesystem with no alignment
becaue XFS makes certain assumptions about how aligned filesystems
are laid out (e.g. AGs always start aligned to a sunit). If the
filesystem is created without alignment, there is a pretty good
chance that it is simply not possible to post-apply alignment to it.
> In these kinds of cases maybe there should be an error logged instead of
> just silently ignoring them?
It does log errors if you already have alignment set and your change
is invalid. If you don't have alignemnt, then they are no-ops and so
are ignored.
> Is there any way to change the superblock? Eg. soething like the ext*
> command:
You can do it with xfs_db, but see above for why it's a bad idea.
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:[~2011-06-09 21:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 16:37 Small files perform much faster on newly formatted fs? Norbert Veber
2011-06-08 7:11 ` Michael Monnerie
2011-06-08 12:26 ` Norbert Veber
2011-06-08 13:47 ` Michael Monnerie
2011-06-08 18:58 ` Norbert Veber
2011-06-09 5:44 ` Michael Monnerie
2011-06-08 20:52 ` Eric Sandeen
2011-06-08 21:16 ` Eric Sandeen
2011-06-09 1:29 ` Dave Chinner
2011-06-09 8:22 ` Christoph Hellwig
2011-06-09 13:48 ` Norbert Veber
2011-06-09 16:30 ` Michael Monnerie
2011-06-09 20:30 ` Norbert Veber
2011-06-09 21:17 ` Dave Chinner [this message]
2011-06-10 0:54 ` Norbert Veber
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=20110609211731.GT32466@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--cc=nveber@pyre.virge.net \
--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