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
On 12/02/2010 09:55, Andrew Gabriel wrote:
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?
You could try using
Darren J Moffat wrote:
On 12/02/2010 09:55, Andrew Gabriel wrote:
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?
You
I have two snv_126 systems. I'm trying to zfs send a recursive snapshot
from one system to another:
# zfs send -v -R tww/opt/chro...@backup-20091225 |\
ssh backupserver zfs receive -F -d -u -v tww
...
found clone origin tww/opt/chroots/a...@ab-1.0
receiving incremental stream of
Hallo.
I'm trying do zfs send -R from a S10 U6 Sparc system to a Solaris 10 U7 Sparc
system. The filesystem in question is running version 1.
Here's what I did:
$ fs=data/oracle ; snap=transfer.hot-b ; sudo zfs send -R $...@$snap |
sudo rsh winds07-bge0 zfs create rpool/trans/winds00r/${fs%%/*}
Alexander Skwar wrote:
Hallo.
I'm trying do zfs send -R from a S10 U6 Sparc system to a Solaris 10 U7 Sparc
system. The filesystem in question is running version 1.
Here's what I did:
$ fs=data/oracle ; snap=transfer.hot-b ; sudo zfs send -R $...@$snap |
sudo rsh winds07-bge0 zfs create
