On Thu, Oct 05, 2006 at 08:55:26PM -0700, Andrew Morton wrote: > On Thu, 05 Oct 2006 13:23:30 -0500 > Dave Kleikamp <shaggy@xxxxxxxxxxxxxx> wrote: > > > I have rebuilt the ext4/jbd2 patches against linux-2.6.19-rc1. The > > patch set is located at > > ftp://kernel.org/pub/linux/kernel/people/shaggy/ext4/2.6.19-rc1/ext4-patches-2.6.19-rc1.tar.gz > > > > So let me see if I have this right. > > You grab Alexandre's kit from http://www.bullopensource.org/ext4/20060926/ > and a plain old `mke2fs -j' gives a filesystem which will mount as ext3 or > ext4. > > If you then mount this filesystem with `-t ext4dev -o extents', it becomes > incompatible with the ext3 driver. Yes? I agree that's the wrong behaviour, and I've always hated the idea of using using mount -o options to enable ext3/4 features. (When do it with EA's and acl's, sigh, and that's wrong too, but at least I was able to paper over that later by adding default mount option support into the superblock.) The right way to do this is to only enable a feature like extents after using tune2fs -O extents, or creating a filesystem with mke2fs -O extents. Can we change the patches to do this, please? - Ted - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
