What you say is true.

BTW, I nearly fell off my chair when I saw that you, one of the true Unix
monuments on this list, showed mild signs of approval of propagation on
close, instead of write!


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen C.
> Tweedie
> Sent: Thursday, November 02, 2000 1:56 AM
> To: Peter J. Braam
> Cc: Stephen C. Tweedie; [EMAIL PROTECTED]; Harrison Xing
> Subject: Re: nesting transactions
>
>
> Hi,
>
> On Wed, Nov 01, 2000 at 10:15:41PM -0800, Peter J. Braam wrote:
>
> > > 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.
>
> But writing a log record before the first write is sufficient for
> that, isn't it?  You don't have to make the whole series of writes
> atomic, just to record that the application has modified the file
> since it was cached.
>
> > 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.
>
> Nice.
>
> 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