On Tue, Jan 27, 2009 at 01:42:31PM +0000, Nick Warne wrote: > > Jan 27 12:54:57 sauron kernel: EXT3-fs: sda2: couldn't mount because of unsupported optional features (40). > Jan 27 12:54:57 sauron kernel: VFS: Mounted root (ext4 filesystem) readonly. > > i.e. root / -> /dev/sda2 couldn't mount, but it does mount, and system > boots normally and functions fine. That's normal; what happens is that the kernel tries to mount it as ext3 first, which takes a pass since it can't support certain filesystems features, and then ext4 mounts it. The ext4 filesystem code will happily mount an ext3 filesystem, so that's why the kernel tries ext3 first. The idea is that for people who are conservative, and have some filesystems using ext3 and some using ext4 (to try out, for example), and then they compile a kernel with both ext3 and ext4, if the root filesystem only has ext3 features, it should be mounted with ext3, not ext4; so the kernel tries ext3 first. If however, you do not compile in ext3 support, the ext4 filesystem code will happily mount an ext3 filesystem --- and in the latest 2.6.29-rc series, the ext4 filesystem code can even happily mount an ext2 filesystem. You will get some of the advantages of ext4's delayed allocation support with ext2/ext3 filesystems, and it would also allow you to only have one extX filesystem compiled into the kernel. But of course, ext4 is still relatively new, and some people like to be conservative with their filesystem choices, and so that's why it's unlikely the ext3 filesystem code will be disappearing from the kernel, even though the ext4 filesystem code is a superset of ext3's functionality. - 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
