On Sun, Jan 04, 2009 at 08:21:06PM +0100, Geert Uytterhoeven wrote: > On Sun, 4 Jan 2009, Theodore Tso wrote: > > On Sun, Jan 04, 2009 at 02:24:43PM +0000, Duane Griffin wrote: > > > > Is there a way using md/dm/lvm etc to make the source partition R/O and > > > > replay the journal onto a CoW snapshop? Admittedly, not easy to do inside > > > > the 'mount' command itself, but at least it might be workable for LiveCD R/O > > > > mounts and forensics work, where you can *tell* beforehand that's what you > > > > want and can jump through setup games before doing the mount... > > > > > > Yes, something like that is best practice, as I understand it. The > > > LiveCD init scripts could check whether they are about to R/O mount an > > > ext[34] filesystem needing recovery and either refuse with a useful > > > message to the user, or even automatically create and mount a COW > > > snapshot, as you described. They'd still need to warn the user though, > > > since things like remounting R/W wouldn't work as expected. > > > > So what's the use case where people want to be able to mount a > > filesystem needing recovery read/only without running the journal? > > As mentioned before, suspending a laptop (running from hdd), running a live CD, > and expecting everything to work fine when resuming from hdd? Any particular reason why suspend doesn't run the journal during shutdown and leave a clean filesystem? It shouldn't take that long surely. I know it doesn't solve the "it really just crashed" problem, but you don't tend to unsuspend from a crash anyway. Bron ( just curious ) -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html