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? Adam
Since there is no real difference between ext2 and ext3 except for the journal, just mount it as ext2. There is no reason to mount a read only filesystem as ext3 Mark Earnest ~~~~~~~~~~ Senior Systems Programmer Academic Services & Emerging Technologies Penn State University
smime.p7s
Description: S/MIME Cryptographic Signature
