From: Theodore Tso <tytso@mit.edu>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Does "32.1% non-contiguous" mean severely fragmented?
Date: Mon, 22 Oct 2007 09:02:45 -0400 [thread overview]
Message-ID: <20071022130245.GC29220@thunk.org> (raw)
In-Reply-To: <200710222058.FBC09363.tFVJOOSFLHFQMO@I-love.SAKURA.ne.jp>
On Mon, Oct 22, 2007 at 08:58:11PM +0900, Tetsuo Handa wrote:
>
> --- Start VM ---
> --- Suspend VM ---
> [root@sakura Ubuntu7.10]# filefrag Ubuntu7.10.vmem
> Ubuntu7.10.vmem: 751 extents found, perfection would be 5 extents
> [root@sakura Ubuntu7.10]# sync
> [root@sakura Ubuntu7.10]# filefrag Ubuntu7.10.vmem
> Ubuntu7.10.vmem: 3281 extents found, perfection would be 5 extents
> [root@sakura Ubuntu7.10]# filefrag Ubuntu7.10.vmem
> Ubuntu7.10.vmem: 3281 extents found, perfection would be 5 extents
> --- Resume and poweroff VM ---
>
> What? "sync" yields more discontiguous?
What filesystem are you using? ext3? ext4? xfs? And are you using
any non-standard patches, such as some of the delayed allocation
patches that have been floating around? If you're using ext3, that
shouldn't be happening.....
If you use the -v option to filefrag, both before and after the sync,
that might show us what is going on. The other thing is to use
debugfs and its "stat" command to get detailed breakdown of the block
assignments of the file.
Are you sure the file isn't getting written by some background tasks
that you weren't aware of? This seems very strange; what
virtualization software are you using? VMware, Xen, KVM?
- Ted
next prev parent reply other threads:[~2007-10-22 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 1:49 Does \"32.1% non-contigunous\" mean severely fragmented? Tetsuo Handa
2007-10-19 18:52 ` Theodore Tso
2007-10-20 3:39 ` Does "32.1% non-contiguous" " Tetsuo Handa
2007-10-20 13:17 ` Theodore Tso
2007-10-22 11:58 ` Tetsuo Handa
2007-10-22 13:02 ` Theodore Tso [this message]
2007-10-23 10:38 ` Tetsuo Handa
2007-10-23 12:34 ` Theodore Tso
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=20071022130245.GC29220@thunk.org \
--to=tytso@mit.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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;
as well as URLs for NNTP newsgroup(s).