linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Manuel Benitez <rickyb@google.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Tool to view extent metadata
Date: Thu, 09 Jul 2009 16:55:07 -0600	[thread overview]
Message-ID: <20090709225507.GH5073@webber.adilger.int> (raw)
In-Reply-To: <23904f640907091517w10608fa4y9b3b8b3a631217c@mail.gmail.com>

On Jul 09, 2009  15:17 -0700, Manuel Benitez wrote:
> I'm currently evaluating the ext4 allocator and one thing I've come
> across is the lack of a tool that displays the exact structure of the
> extents making up a file. I've found plenty of tools that will tell me
> how many contiguous segments a file contains, but nothing so far to
> let me see the actual makeup of the extents that map the inode to the
> blocks that comprise the file. Have I just missed something obvious,
> or would this be something worth me spending some time doing?
> 
> If so, one option would be to either modify the stat command or add a
> similar command in debugfs to show the extents from the roots through
> the root down to the leafs. Anyone have preferences or opinions?

The "filefrag" tool in recent e2fsprogs should provide such information,
using the FIEMAP ioctl to extract extent information from the kernel.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  reply	other threads:[~2009-07-09 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 22:17 Tool to view extent metadata Manuel Benitez
2009-07-09 22:55 ` Andreas Dilger [this message]
2009-07-13 15:03   ` Manuel Benitez
2009-07-13 15:28     ` Eric Sandeen
2009-07-13 19:27     ` Andreas Dilger
2009-07-10  5:19 ` Aneesh Kumar K.V

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=20090709225507.GH5073@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rickyb@google.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;
as well as URLs for NNTP newsgroup(s).