Re: replay on read-only filesystem

Jeff Chua (jeffchua@silk.corp.fedex.com)
Mon, 25 Jun 2001 08:32:23 +0800 (SGT)


On Mon, 25 Jun 2001, Anthony Heading wrote:
> Did you get a satisfactory answer? I'd be interested to know...

Here's what I got from Alan. I've "crashed" my system quite a quite time
by yanking out the power plug, and so far, the system is still ok.
Much better than ext2 as there's no fsck.

Jeff

------------------------------------------------------
From: Alan Cox <alan@lxorguk.ukuu.org.uk>

> what's the impact of mounting reiserfs as Read-Only (specified in
fstab)?
> >From syslog ...
>
> Jun 24 01:10:30 boston kernel: Warning, log replay starting on readonly
> filesystem
>
> Is this a problem?

In normal configurations it shouldnt be. Both ext3 and reiserfs currently
have the problem that they need to replay the log to get a stable file
system. Obviously you cant replay the log to disk if its read only, so
they replay the log to disk read/write then mount the fixed fs read only.

It breaks if your hardware has given up writing (certain disk fails) or if
you are running the swsuspend patch (serious disk corruption) but really
the swsusp patch interaction is the only problem one

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/