Subject: Re: DEV_B_SIZE
To: Steve Byan <email@example.com>
From: Julian Elischer <firstname.lastname@example.org>
Date: 01/31/2003 11:42:53
On Fri, 31 Jan 2003, Steve Byan wrote:
> On Friday, January 31, 2003, at 01:16 PM, Julian Elischer wrote:
> > Recovery algorythms might have to deal with this (should we actually
> > decide to write one.. :-).
> > Particularly if the block being written was the 1st, but the other 7
> > blocks contain data that the OS has no way of knowing that they are in
> > jeopardy. In other words, I might know that block 1 is in danger and
> > put
> > it in a write log, (in a logging filesystem) but I have no way of
> > knowing that the other 7 are in danger, so they may not be in the write
> > log (assuming thAat the write log only holds the last N transactions.).
> > I'd say that this means that the drive should hold the active 4k block
> > in nvram or something..
> > You seem to have considered this but I'm in agreement that it could
> > prove "nasty" in exactly the cases that are most important..
> > people use write logging etc. in cases where they care about the data
> > and recovery time. these are exactly the people who are going to be the
> > most pissed off to lose their data. ..
> Thanks, may I forward your response on to the committee?
sure.. correct the spelling though :-)