From: Kalpak Shah <kalpak@clusterfs.com>
To: TheodoreTso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@clusterfs.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Change output format of filefrag
Date: Tue, 14 Aug 2007 18:42:45 +0530 [thread overview]
Message-ID: <1187097165.3907.9.camel@garfield> (raw)
Hi,
I am adding FIEMAP support to filefrag and I noticed that current output
format of filefrag can be improved a lot. It is very difficult to add
information like lun, extent type, etc. to such a format.
$ filefrag -v /tmp/abc
Checking /tmp/abc
Filesystem type is: ef53
Filesystem cylinder groups is approximately 296
File is stored in extents format
Blocksize of file /tmp/abc is 1024
File size of /tmp/abc is 10485760 (10240 blocks)
First block: 4609
Last block: 26068
Discontinuity: Block 512 is at 8556 (was 5120)
Discontinuity: Block 517 is at 15729 (was 8560)
Discontinuity: Block 1173 is at 16633 (was 16384)
Discontinuity: Block 9117 is at 24945 (was 24576)
Discontinuity: Block 9125 is at 24954 (was 24952)
/tmp/abc: 6 extents found
I think an output format similar to that of xfs may be better. This is
easier for parsing as well. Like this:
$ filefrag -e {filename}
ext: logical: phys start..end kB: kB :lun: flags
0: [0..151]: 288444888..288445039: 152 : 0 :
1: [152..199]: XXXXXXXX..YYYYYYYYYY: 47 : 0 : hole
2: [200..299]: MMMMMMMM..NNNNNNNNNN: 100 : 0 : unwritten, unknown
Please suggest if this is ok.
Thanks,
Kalpak.
next reply other threads:[~2007-08-14 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 13:12 Kalpak Shah [this message]
2007-08-14 13:43 ` Change output format of filefrag Andreas Dilger
2007-08-14 13:53 ` Alex Tomas
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=1187097165.3907.9.camel@garfield \
--to=kalpak@clusterfs.com \
--cc=adilger@clusterfs.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 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).