On 4-Feb-09, at 1:01 PM, Miles Nordin wrote: ... Here are the > problems, again, with archiving 'zfs send' output: > ... > EXTREMELY corruption-sensitive. 'tar' and zpool images both > detect, report, work around, flipped bits.
I know this was discussed a while back, but in what sense does tar do any of those things? I understand that it is unlikely to barf completely on bitflips, but won't tar simply silently de-archive bad data? Correct me if I'm wrong, but each tar'd object isn't stored with its checksum? Of course your points re: send are well taken, thanks for the synopsis. --Toby _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
