On Tue, 23 Aug 2005, Amos Shapira wrote: > On 8/23/05, Tzafrir Cohen <[EMAIL PROTECTED]> wrote: > > On Tue, Aug 23, 2005 at 01:55:41AM +0300, Diego Iastrubni wrote: > > > Hi all, > > > > > > I have this problem which comes without warning on my box, it seems "/" > > > gets > > > remounted (without any warning, not reason) as read only. I can use the > > > box > > > without real big problems, until something needs to write to the disk (for > > > example konqueror gets a file from the web or something as silly as that). > > > > > > I reboot, and the next thing I see is that / is not clean, and I need to > > > run > > > "fsck -y", which takes a long time since my root-fs is quite large (30GB). > > > > Is it ext2? Bad corruptions on reiserfs give somewhat similar errors but > > with a different message. > > > > The init scripts do that. > > I think he ment that in the middle of work at multi-user level his > root partition gets re-mounted read-only. Not at boot time.
ext3 does this if it encounteres various types of I/O errors - it'll change the device to read-only at this point (without any remount). this will result strange errors to go to /var/log/messages. ofcourse, if the corrupted FS is where /var/log/messages resides, you'll not see any new errors. that's another reason to want to have /var on a seperate partition. it could be that reiserfs has a similar behaviour - but i didn't encounter it personally. -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
