From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: Add a norecovery option to ext3/4? Date: Tue, 10 Apr 2007 14:08:26 +0200 Message-ID: <20070410120825.GA29487@lazybastard.org> References: <20070409000556.GA13980@implementation> <461A5F13.7040705@cfl.rr.com> <461A760B.1040103@redhat.com> <20070410072253.GA28665@lazybastard.org> <20070410112718.GF13650@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE To: Theodore Tso , Eric Sandeen , Phillip Susi , Samuel Thibault , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Content-Disposition: inline In-Reply-To: <20070410112718.GF13650@thunk.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Tue, 10 April 2007 07:27:18 -0400, Theodore Tso wrote: >=20 > I suppose what you could do is to read in the journal, and use it to > create an remapping table so that when you want to read block #5126, > and block number 5126 is in the journal, to read the journal version > of the block instead of the one on disk. That would allow for safe > access to a filesystem being mounted read-only without the journal > being present. Another option would be to access the medium through a mapping inode, replay the journal into the mapping inode and _not_ flush the dirty pages. But as long as a remapping table is sufficient for ext3 journal format, such a table should be simpler and faster. > Patches gratefully accepted.... Not likely to come from me anytime soon. There's a certain other filesystem I have to finish first that still suffers from the same problem. J=C3=B6rn --=20 Do not stop an army on its way home. -- Sun Tzu