> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Mason
> Sent: Tuesday, October 31, 2000 7:18 AM
> To: Stephen C. Tweedie
> Cc: Peter J. Braam; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: nesting transactions
>
>
> Yes, I was less than clear ;-)  I meant that a crash could result in a
> fully consistent filesystem with file writes that are not reflected in the
> intermezzo log.  This is not a huge issue, but it gets more interesting
> when you turn off data logging (and the ext3 code that flushes new blocks
> before transaction commit).  One client has a bigger file with bogus data,
> and another has a smaller file with good data, and intermezzo has no log
> entries to help figure out which one is right.
>
> It seems like intermezzo could log at the start and end of each write, or
> rely on an atomic write flag provided by the filesystem.  Depending on the
> total size of the write, there should be cases where each one is faster
> than the other.
>

This is a nice idea that has occured to me a few times. Is it expensive mark
the beginning and end of a write transaction, maybe not?

- Peter -



> -chris
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-fsdevel" in
> the body of a message to [EMAIL PROTECTED]
>

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]

Reply via email to