Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757914AbZADW4N (ORCPT ); Sun, 4 Jan 2009 17:56:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751967AbZADWz5 (ORCPT ); Sun, 4 Jan 2009 17:55:57 -0500 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:42777 "EHLO out2.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751735AbZADWz4 (ORCPT ); Sun, 4 Jan 2009 17:55:56 -0500 X-Greylist: delayed 798 seconds by postgrey-1.27 at vger.kernel.org; Sun, 04 Jan 2009 17:55:56 EST Date: Mon, 5 Jan 2009 09:42:33 +1100 From: Bron Gondwana To: Geert Uytterhoeven Cc: Theodore Tso , Duane Griffin , Valdis.Kletnieks@vt.edu, Martin =?utf-8?Q?MOKREJ=C5=A0?= , Pavel Machek , kernel list , Andrew Morton , mtk.manpages@gmail.com, rdunlap@xenotime.net, linux-doc@vger.kernel.org Subject: Re: document ext3 requirements Message-ID: <20090104224233.GA9531@brong.net> References: <495FEE66.9080903@ribosome.natur.cuni.cz> <495FF9CE.2020908@ribosome.natur.cuni.cz> <495FFECB.5040001@ribosome.natur.cuni.cz> <15786.1231041158@turing-police.cc.vt.edu> <20090104184040.GC17558@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: brong.net User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1844 Lines: 35 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-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/