Date: Mon, 22 Jan 2007 10:29:18 -0800 From: perryh@pluto.rain.com To: vd@freebsd.org Cc: freebsd-hackers@freebsd.org, xride@x12.dk Subject: Re: Where to start? Message-ID: <45b5027e.g8Hs/VOZs%2B63TD6V%perryh@pluto.rain.com> In-Reply-To: <20070122083727.GA61615@qlovarnika.bg.datamax> References: <20070119201935.GA60202@x12.dk> <20070120024614.E99400@odysseus.silby.com> <20070122083727.GA61615@qlovarnika.bg.datamax>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I'd like to see the ability to run gjournal without reformatting. > > If you could create a dummy file inside the filesystem, then use > > that area for the journal, it might be possible ... > > I am not sure about gjournal internals but what if a system crash > occurs in the middle of a transaction and the fs gets corrupted > and the data, necessary to fix it is in the journal, but you > cannot access the journal because the file, which contains the > journal, is on a corrupted fs? Looking at this as purely a data-integrity problem, and knowing nothing whatsoever about gjournal internals :) I would guess that if a way could be found to preallocate the journal space (as with mkfile(8) in sufficiently-old systems), and then record its location in a reasonably-secure location (the superblock?), it could be accessed during recovery without reference to possibly-corrupt filesystem metadata.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45b5027e.g8Hs/VOZs%2B63TD6V%perryh>