linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: extent counting fun
Date: Mon, 05 Jul 2010 14:24:52 -0500	[thread overview]
Message-ID: <4C323184.8020401@redhat.com> (raw)

[root@host ~]# filefrag -B /mnt/test/file
/mnt/test/file: 34 extents found
[root@host ~]# filefrag /mnt/test/file
/mnt/test/file: 1058 extents found, perfection would be 1 extent

Hum, is it 34 or 1058? :)

Older filefrag counted contiguous metadata as part of a contiguous
extent... newer filefrag works in fiemap query-only mode by default,
and just takes what fiemap tells it.  The inconsistency is weird
though, and led to a Red Hat bug that I'm inclined to NOTABUG... but
do people think this needs to be made any more consistent?

Should we hack ext3_fiemap() to include the checks for contiguous
metadata?  Or was that too shady/clever to start with ...? :)

-Eric

             reply	other threads:[~2010-07-05 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 19:24 Eric Sandeen [this message]
2010-07-05 23:46 ` extent counting fun Andreas Dilger
2010-07-06  0:50   ` Eric Sandeen
2010-07-09 21:10     ` Andreas Dilger

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=4C323184.8020401@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).