From: Pavel Machek Subject: Re: Add a norecovery option to ext3/4? Date: Sun, 15 Apr 2007 18:49:29 +0000 Message-ID: <20070415184929.GC10097@ucw.cz> References: <20070409000556.GA13980@implementation> <461A5F13.7040705@cfl.rr.com> <461A760B.1040103@redhat.com> <461BDD48.2000904@cfl.rr.com> <461BE2FB.5090101@redhat.com> <461D407C.3030706@tmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Eric Sandeen , Phillip Susi , Samuel Thibault , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, joern@lazybastard.org, tytso@mit.edu To: Bill Davidsen Return-path: Received: from gprs189-60.eurotel.cz ([160.218.189.60]:3840 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753532AbXDOT5k (ORCPT ); Sun, 15 Apr 2007 15:57:40 -0400 Content-Disposition: inline In-Reply-To: <461D407C.3030706@tmr.com> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Hi! > >You might not damage the underlying filesystem, but you > >could sure go > >off in the weeds trying to read it, if you stumbled > >upon some > >half-updated metadata... so while it may be safe for > >the filesystem, I'm > >not convinced that it's safe for the host reading the > >filesystem. > > > Exactly. If the data are protected you can use other > software to access it. For ext3 an explicit ext2 mount > might do it... It does not :-(. dirty ext3 is marked incompatible with ext2. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html