Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
- From: Matthew Wilcox <matthew@xxxxxx>
- Date: Fri, 9 Jun 2006 09:31:16 -0600
On Fri, Jun 09, 2006 at 07:28:22PM +0400, Alex Tomas wrote:
JG> "ext3" will become more and more meaningless. It could mean _any_ of
JG> several filesystem metadata variants, and the admin will have no clue
JG> which variant they are talking to until they try to mount the blkdev
JG> (and possibly fail the mount).
debugfs <dev> -R stats | grep features ?
... a simple and intuitive command which just trips off the tongue.
I want extents, but I'm still unconvinced that ext3 needs to grow beyond
32-bit blocks. The scheme posted by Val and Arjan (with the
continuation inodes) seems much neater.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [RFC 0/13] extents and 48bit ext3
- From: Mingming Cao
- Re: [RFC 0/13] extents and 48bit ext3
- From: Jeff Garzik
- Re: [RFC 0/13] extents and 48bit ext3
- From: Andreas Dilger
- Re: [RFC 0/13] extents and 48bit ext3
- From: Jeff Garzik
- Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
- From: Alex Tomas
- [RFC 0/13] extents and 48bit ext3
- Prev by Date: Re: [PATCH 1/6] IPC namespace core
- Next by Date: Re: [PATCH][INCOMPLETE] sata_nv: merge ADMA support
- Previous by thread: Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
- Next by thread: Continuation Inodes Explained! (was Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3)
- Index(es):
Relevant Pages
|
