[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090727143413.GF17272@mit.edu>
Date: Mon, 27 Jul 2009 10:34:13 -0400
From: Theodore Tso <tytso@....edu>
To: Eric Sandeen <sandeen@...hat.com>
Cc: Curt Wohlgemuth <curtw@...gle.com>,
ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] Print extent information in debugfs
On Sun, Jul 26, 2009 at 10:18:02PM -0500, Eric Sandeen wrote:
>
> Perhaps a bit late, but I find the "#<extent length>" reporting very
> unintuitive. Doesn't "#X" usually imply ordering? How about:
>
> (0-60 [61b]): 342272-342332, (61-127 [67b,uninit]): 537822-537888
>
> ... or maybe some other ideas. IMHO it's all a bit hard to read anyway
> unless it's printed in a table format ala the new filefrag output.
That's a good idea. I've switched it to use a table format:
Level Entries Logical Physical Length Flags
0/ 0 1/ 2 0 - 60 342272 - 342332 61
0/ 0 2/ 2 61 - 127 537822 - 537888 67 Uninit
and
Level Entries Logical Physical Length Flags
0/ 2 1/ 4 1 - 274323 24844 274323
1/ 2 1/ 84 1 - 387 8458 387
2/ 2 1/ 84 1 - 1 10242 - 10242 1
2/ 2 2/ 84 4 - 4 10245 - 10245 1
2/ 2 3/ 84 8 - 8 10249 - 10249 1
I've also simplified the debugfs stat output so it looks more like the
"BLOCKS" output:
mtime: 0x4a6d164e:861ee098 -- Sun Jul 26 22:51:58 2009
crtime: 0x4a6d164e:82c08b38 -- Sun Jul 26 22:51:58 2009
Size of extra inode fields: 28
EXTENTS:
(0-60): 342272-342332, (61-127 [uninit]): 537822-537888
Hopefully that's easier for everyone to understand.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists