Mark wrote on 09/06/2009 11:02:22 AM: > > Second (as Mark noted) - you may think you can mount the FS R/O and prevent > > the log from being replayed by specifying you want a non-journaled FS (aka > > EXT2) - which may (and will) lead to the FS being marked dirty (as Shane > > noted) - requiring a 'fsck' to be performed - requiring WRITE access (bad.. > > very bad !) > > The fsck is _not_ required, so write access is not required.
Sorry Mark, I'm in agreement with Ivan. I just did a test on x86 as at the moment I don't have a zLinux system I can break filesystems on. If you attempt to mount a *clean* ext3 f/s as ext2 you get the warning - and a successful mount. With a dirty journal it refuses to mount as ext2 (ro *or* rw). A subsequent mount as ext3 (ro) runs the journal regardless as has been discussed I think. It shows as ro in /proc/mounts. Shane ... ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
