Hello again from Gregg C Levine Adam, just for fun, what sort of hardware are you running this under? And is it Debian? Or somebody else? Yeah, try it. Mount the pack, R/O, and see what happens, and let us know what happens.
------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda ) > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of > Adam Thornton > Sent: Friday, December 06, 2002 1:37 AM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] Ext3 oddity > > On Fri, Dec 06, 2002 at 12:38:55PM +0800, John Summerfield wrote: > > > Okay, use '-f' to force it to check. Just in case. It is telling you > > the dirty bit's not set and that means nobody else has it mounted rw. > > > I have seen e2fsck find errors when forced to check, even though the > > filesystem was supposedly clean. After that I'm out of iudeas. > > Well, it causes a WHOLE BUNCH of the same sort of CCW errors (not > surprisingly). But lots (orders of magnitude) more than when I just > mount it as ext3. > > I'm pretty convinced that mounting an ext3 filesystem attempts to write > to the journal inode, even if you want to mount the filesystem r/o. I > consider this a bug. Maybe I'll look at the code tomorrow. > > I also wonder what happens if I set the device node to be r/o. > > Adam
