On Thu, Dec 05, 2002 at 03:24:00PM -0500, Adam Thornton wrote: > If you have a shared volume, linked read-only, to a virtual machine, > formatted with ext3, then even if you have it specified as ro in > /etc/fstab, you still get errors at boot, presumably as it tries to do > something with the journal inode. > > If you mount it as ext2 these errors do not appear, > > Shouldn't ext3 see that it's being mounted read-only, and not attempt to > manipulate the journal?
This is known to work, as long as no journal recovery is needed. My guess is that the journal needs to be replayed. If possible, mount the filesystem read-write elsewhere, let it replay the journal (watch the kernel messages), and then try again. -- - mdz
