From: Andreas Dilger <adilger@sun.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Girish Shilamkar <Girish.Shilamkar@sun.com>,
Theodore Tso <tytso@mit.edu>,
Ext4 Mailing List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsprogs: Dump extent/sindices using debugfs
Date: Thu, 12 Jun 2008 02:32:04 -0600 [thread overview]
Message-ID: <20080612083204.GU3726@webber.adilger.int> (raw)
In-Reply-To: <20080611104351.GA9008@skywalker>
On Jun 11, 2008 16:13 +0530, Aneesh Kumar K.V wrote:
> On Wed, Jun 11, 2008 at 03:41:28PM +0530, Girish Shilamkar wrote:
> > The attached patch adds a command to debugfs to display all the
> > extents/indices contained in an inode or the block specified.
> > The options to the command includes tranversing and dumping the entire
> > extent tree (if inode specified) or the branch (in case of block) and
> > can display only the headers if required.
> >
> > Would you please let me know your comments/suggestions ?
>
> lib/ext2fs/tst_extents (I don't know why we don't install this by
> default) have inode, root and ns/n command which help to iterate the
> extent format inode
The "tst_*" programs are purely for regression testing. Having this
functionality built into a proper tool like debugfs is needed.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-06-12 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 10:11 [PATCH] e2fsprogs: Dump extent/sindices using debugfs Girish Shilamkar
2008-06-11 10:43 ` Aneesh Kumar K.V
2008-06-12 8:32 ` Andreas Dilger [this message]
2008-06-12 13:46 ` 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=20080612083204.GU3726@webber.adilger.int \
--to=adilger@sun.com \
--cc=Girish.Shilamkar@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.