Dick Hoogendijk wrote:
Some time ago there was some discussion on zfs send | rcvd TO A FILE.
Apart form the disadvantages which I now know someone mentioned a CHECK
to be at least sure that the file itself was OK (without one or more
bits that felt over). I lost this reply and would love to hear this
check again. In other words how can I be sure of the validity of the
received file in the next command line:
# zfs send -Rv rp...@090902 > /backup/snaps/rpool.090902
I only want to know how to check the integrity of the received file.
You should be able to generate a sha1sum/md5sum of the zfs send stream
on the fly with 'tee':
# zfs send -R rp...@090902 | tee /backups/snaps/rpool.090902 | sha1sum
compare the output of that with the sha1sum of the file on-disk:
# sha1sum /backups/snaps/rpool.090902
This only guarantees that the file contains the exact same bits as the
zfs send stream. It does not verify the ZFS format/integrity of the
stream - the only way to do that is to zfs recv the stream into ZFS.
--
Dave
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
