Hello all, Commit a85f8350 (http://goo.gl/aCykm) makes it impossible to fsck an ext4 filesystem w/ external journal if it is mounted read-only. Certain distros (Gentoo in my case) expect to be able to do this on the root filesystem at boot time, and get very upset if they can't. With journal checks forced now, e2fsck tries to open() the external journal device, which always fails with -EBUSY if the filesystem is mounted, read-only or otherwise. Is this the expected behavior? Maybe the kernel shouldn't be returning an error there? It's been doing so since at least v3.6. Clearly this doesn't impact many people, since it's been in the tree for almost a year now... but I thought I'd mention it. Thoughts? Thanks very much, Calvin -- 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
