From: John Lister <john.lister@kickstone.com>
To: xfs@oss.sgi.com
Subject: Re: XFS defragmentation issue
Date: Sat, 11 Sep 2010 07:55:32 +0100 [thread overview]
Message-ID: <4C8B27E4.2050102@kickstone.com> (raw)
In-Reply-To: <4C8A4395.5070702@kickstone.com>
Stan Hoeppner wrote on 9/10/2010 14:00
>>On 10/09/2010 15:41, John Lister wrote:
>> Hi, using ubuntu 9.04, kernel version 2.6.28-18 and xfsprog
v2.10.2-1 I'm trying to defragment a drive. If I use xfs_db to check for
fragmentation it shows for >>example that a file has 20k+ fragments:
>>inode 578505506 actual 23240 ideal 1
>>
>>mapping the inode to the file and running xfs_frs states that the
file is fully defragmented.
>>
>>Also running xfs_frs says the drive is defragmented while xfs_db for
example reports 300k fragments.
>>
>>Which is right? and is it possible to defragment the file assuming it
is fragmented so badly, if so how?
>Try unmounting and remounting the filesystem, and see if the various
>tools all report the same thing afterwards. This solved the exact same
>problem for me very recently, though I'm on kernel 2.6.34.1 and xfsprogs
>2.9.8.
Cheers, that got rid of most of it, there is still a slight discrepency
(50 extra fragments) which I can live with.
John
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-11 6:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 14:41 XFS defragmentation issue John Lister
2010-09-10 19:00 ` Stan Hoeppner
2010-09-11 6:55 ` John Lister [this message]
2010-09-11 8:23 ` Dave Chinner
2010-09-11 8:25 ` John Lister
2010-09-11 19:38 ` Stan Hoeppner
2010-09-11 19:57 ` Iustin Pop
2010-09-12 1:01 ` Dave Chinner
2010-09-12 8:43 ` Emmanuel Florac
2010-09-12 9:45 ` Stan Hoeppner
2010-09-13 8:05 ` Roel van Meer
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=4C8B27E4.2050102@kickstone.com \
--to=john.lister@kickstone.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.