From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Fedyk Subject: Re: reiserfs logging patches udpated Date: Tue, 30 Mar 2004 11:06:06 -0800 Message-ID: <4069C51E.90505@matchmail.com> References: <1080149399.14737.77.camel@watt.suse.com> <20040324143516.3162cbfe.akpm@osdl.org> <1080168379.14743.124.camel@watt.suse.com> <200403250147.54246.bernd-schubert@web.de> <40625867.4060800@matchmail.com> <1080224062.26677.3.camel@watt.suse.com> <406343F1.2050504@matchmail.com> <1080247847.2926.0.camel@watt.suse.com> <4068203E.4050700@namesys.com> <40686FA2.1010501@matchmail.com> <16489.43908.702818.688887@laputa.namesys.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <16489.43908.702818.688887@laputa.namesys.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Nikita Danilov Cc: Hans Reiser , Chris Mason , Bernd Schubert , reiserfs-list@Namesys.COM, Andrew Morton Nikita Danilov wrote: > Mike Fedyk writes: > > [...] > > > > > The basic idea of virtual vs block journals, is that instead of using a > > few bytes to describe what you're changing in (for instance) the inode > > table (or equivalent), ext3 (and reiser3 thanks to info from Chris > > Mason) copies entire inode table block (usually 1-4k depending on block > > size) into the journal. > > Unless I am missing something this is called "logical logging" (as > opposed to the "physical logging") in the data-base literature. Yes, thanks for pointing that out. I had forgotten the correct term (and mentioned that in my first message about that at the time). "Virtual" was the best approximation I could think of when I was writing that up. Mike