As Casper pointed out, the right thing to do is to build applications
such that they can detect mid-transaction state and roll it back (or
forward, if there's enough data). Then mid-transaction snapshots are
fine, and the lack of APIs by which to inform the filesystem of
application transaction bo
--- erik.trim...@oracle.com wrote:
|> So, if your apps have to be programmed to be
|> versioning/consistency/checkmarking aware in any case, how
|> would having a fancy Versioning filesystem be any better
|> than using what we do now?
|> (i.e. svn/hg/cvs/git on top of ZFS/btrfs/et al)
|> Z
