From: David Chinner <dgc@sgi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com, apiszcz@solarrain.com
Subject: Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume
Date: Wed, 30 May 2007 10:41:40 +1000 [thread overview]
Message-ID: <20070530004140.GX85884050@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705291404430.2944@p34.internal.lan>
On Tue, May 29, 2007 at 02:05:44PM -0400, Justin Piszcz wrote:
> # uname -a
> Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux
> # xfs_fsr -V
> xfs_fsr version 2.2.38
> # xfs_db -V
> xfs_db version 2.8.18
> # xfs_db -c frag -f /dev/md1
> actual 449, ideal 403, fragmentation factor 10.24%
> # xfs_fsr /dev/md1
> /d2 start inode=0
> # xfs_db -c frag -f /dev/md1
> actual 449, ideal 403, fragmentation factor 10.24%
> #
Try xfs_db -c "frag -v" -f /dev/md1 to see which inodes are
fragmented, then run xfs_db -c "inode <num>" -c bmap -f /dev/md1
to see whether it is a sparse file or not....
Remember - xfs_fsr does best effort defrag - if it can't make
progress, it does nothing, and it can't defrag directories...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-05-30 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 18:05 xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume Justin Piszcz
2007-05-30 0:41 ` David Chinner [this message]
2007-05-30 2:25 ` Chris Wedgwood
2007-05-30 8:45 ` Justin Piszcz
2007-05-30 8:45 ` Justin Piszcz
2007-05-30 2:41 ` Eric Sandeen
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=20070530004140.GX85884050@sgi.com \
--to=dgc@sgi.com \
--cc=apiszcz@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--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