Can anyone suggest how I can get around the above error when sending/receiving a ZFS filesystem? It seems to fail when about 2/3rds of the data have been passed from send to recv. Is it possible to get more diagnostics out?

This filesystem has failed in this way for a long time, and I've ignored it thinking something might get fixed in the future, but this hasn't happened yet. It's a home directory which has been in existence and used for about 3 years. One thing is that the pool version (3) and zfs version (1) are old - could that be the problem? The sending system is currently running build 125 and receiving system something approximating to 133, but I've had the same problem with this filesystem for all builds I've used over the last 2 years.

--
Cheers
Andrew Gabriel
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to