Michael Herf wrote:
I replayed a bunch of filesystems in order to get dedupe benefits.
Only thing is a couple of them are rolled back to November or so (and
I didn't notice before destroy'ing the old copy).
I used something like:
zfs snapshot pool/f...@dd
zfs send -Rp pool/f...@dd | zfs recv -d pool/fs2
(after done...)
zfs destroy pool/fs
zfs rename pool/fs2/fs pool/fs
What are the failure modes for "partial" send/recv? I've experienced
full rollbacks when the process is canceled.
But my case feels like the stream became truncated and the filesystem
ended up partially built? Is this an expected result?
Individual receives should be atomic.
It does seem like ZFS needs a way to do this kind of operation
atomically in the future, but I'm more interested in understanding if
there's something I did wrong using the current tools, or if there are
bugs.
Was there any error output? I always use -v on recursive receives to
track progress.
--
Ian.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
