>Got it, my assumption is undelete would only act on deleted files. >Truncating, changing the files data are not delete operations (unlink). >You are starting to talk about versioning at that point -- in which case >this issue becomes way more complicated. Applications may do multiple >writes to a file with the intent of one transaction, there is no way to >tell that the three or four writes leave the file in a "broken" state until >the fifth write happens, the app may be watching and handling this >transitory state and there is no shared knowledge of its current state.
Quite; of course, ZFS snapshots allow you to capture any type of modification, including truncation or removal. I can not think of a clear transaction boundary other than close and fsync. Casper _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
