lkml.org 
[lkml]   [2001]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Journaling: Surviving or allowing unclean shutdown?
On Thu, Jan 04, 2001 at 07:21:04PM +0000, Stephen C. Tweedie wrote:

> ext3 does the recovery automatically during mount(8), so user space
> will never see an unrecovered filesystem. (There are filesystem flags
> set by the journal code to make sure that an unrecovered filesystem
> never gets mounted by a kernel which doesn't know how to do the
> appropriate recovery.)

I did not follow the ext3 development recently, how did you solve
the "read-only mount(2) (optionally on write protected media)" issue ?

Does the mount fail, or does the code virtually replays (without writing)
only ?

I think any other action (only replaying on rw mount and presenting
a broken filesystem on ro) is quite fatal, at least if I think of
a replay on -remount,rw :)

Also, an unconditional hidden replay even if "ro" is specified is not nice.

This is especially critical on root filesystem, because there is IMHO
no way to specify mount arguments to the "/" mount, except ro/rw.

--

ciao -
Stefan

" ( cd /lib ; ln -s libBrokenLocale-2.2.so libNiedersachsen.so ) "

Stefan Traby Linux/ia32 fax: +43-3133-6107-9
Mitterlasznitzstr. 13 Linux/alpha phone: +43-3133-6107-2
8302 Nestelbach Linux/sparc http://www.hello-penguin.com
Austria mailto://st.traby@opengroup.org
Europe mailto://stefan@hello-penguin.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:52    [W:0.146 / U:1.116 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site