Hi Stephen,

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen C.
> Tweedie
> Sent: Wednesday, November 01, 2000 2:01 PM
> To: Peter J. Braam
> Cc: [EMAIL PROTECTED]; Stephen Tweedie
> Subject: Re: nesting transactions
>
>
> Hi,
>
> On Tue, Oct 31, 2000 at 09:35:42PM -0800, Peter J. Braam wrote:
> >
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Mason
> > > 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?
>
> Will it really help?  A single application write() is usually not an
> interesting atom as far as file consistency is concerned --- files
> will usually be written chunk by chunk, and it really is open/close
> which mark consistent states, not write()s.

Yes - it would, because the log would now at least know that the file has
changed.

BTW, for the slightly longer future we have rather nicer plans for this.
With SnapFS (see sourceforge project snapfs for code - which is beginning to
work), InterMezzo can dynamically handle versioning conflicts by creating a
snapshot on the fly and introduce branches for different modifications.

A file comparison tool like draksync can now allow a user to easily sort out
conflicts, and remove the branches from the snapshots.

- Peter -


>
> Cheers,
>  Stephen
> -
> 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