Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
Chase Venters <[email protected]>
| Newsgroups | gmane.linux.file-systems,gmane.comp.file-systems.ext2.devel,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 9 Jun 2006, Joel Becker wrote: > Heck, forget the name, just make the breakage more explicit. Do > it at mkfs/tunefs time. "tunefs -extents" or "mkfs -t ext3 -extents". > A mount option assumes that you can do with or without it. If you do it > once, you can mount the next time without it and stuff Just Works. Even > htree follows this. A clean unmount leaves a clean directory structure > that a non-htree driver can use. I suggested this somewhere back in the thread and it got no play. What's the problem with doing things this way? (Aside from it being a compromise that doesn't automatically result in a new ext4) Of course, there are a few debates going on here. Only one of them is about compatibility. > > Joel > Cheers, Chase - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html