From: Andreas Dilger <adilger@sun.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org, Kalpak Shah <Kalpak.Shah@sun.com>
Subject: Re: Bug in delayed allocation: really bad block layouts!
Date: Mon, 18 Aug 2008 03:50:12 -0700 [thread overview]
Message-ID: <20080818105012.GP3040@webber.adilger.int> (raw)
In-Reply-To: <489FCFD4.2050602@redhat.com>
On Aug 11, 2008 00:36 -0500, Eric Sandeen wrote:
> Theodore Tso wrote:
> > One of
> > the things I've been meaning to do is to clean up the output of
> > filefrag so that it's a bit easier to parse. It's really stupid for
> > it to print "file is in extents format" over and over again...
>
> I'm not really even sure why it should print it at all, ever, at least
> without -vvv or something. (That's what I meant to filter the first
> time ;) If the tool is to report layout I'm not sure the trivia about
> how the layout is tracked internally is all that interesting. The
> fiemap patches for filefrag that print it out more as a table format,
> more like xfs_bmap does, should be a lot better. But anyway...
Actually, the FIEMAP patches for filefrag provide a much nicer format
for the output, more like what xfs_bmap does. For now it only does
this if requested with the "-e" option (--extents) but if Ted is not
adverse to changing the output format of filefrag we could make it the
default.
The whole Lustre patchset (against 1.40.11) is at
http://downloads.lustre.org/public/tools/e2fsprogs/latest/e2fsprogs-1.40.11-sun1-patches.tar.gz
but Kalpak or I can send just the FIEMAP one again if you are interested.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-08-18 10:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 17:30 Bug in delayed allocation: really bad block layouts! Theodore Ts'o
2008-08-10 17:54 ` Eric Sandeen
2008-08-10 18:22 ` Theodore Tso
2008-08-10 18:54 ` Eric Sandeen
2008-08-10 20:04 ` Eric Sandeen
2008-08-11 1:46 ` Theodore Tso
2008-08-11 5:36 ` Eric Sandeen
2008-08-18 10:50 ` Andreas Dilger [this message]
2008-08-10 18:28 ` Theodore Tso
2008-08-11 7:55 ` Aneesh Kumar K.V
2008-08-11 14:39 ` Aneesh Kumar K.V
2008-08-11 18:15 ` Aneesh Kumar K.V
2008-08-13 2:32 ` Theodore Tso
2008-08-13 10:52 ` Aneesh Kumar K.V
2008-08-14 21:49 ` Mingming Cao
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=20080818105012.GP3040@webber.adilger.int \
--to=adilger@sun.com \
--cc=Kalpak.Shah@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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 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).