Error in rsync protocol data stream (code 12) when doing local
rsync.
Mike Rubel
mrubel at galcit.caltech.edu
Tue Aug 6 14:13:02 EST 2002
Philip,
I don't know whether this will help, but I did run into an error very much
like this one in a similar situation. The problem was corruption in the
target filesystem, which I was able to fix with e2fsck. Have you tried
that?
Mike
> I systematically get the following errors:
>
> # rsync --archive -v /etc /mnt/hdf/
> building file list ... done
> etc/
> etc/mtab
> etc/ntp/drift
> etc/vmware/vmnet8/dhcpd/dhcpd.leases
> etc/vmware/vmnet8/dhcpd/dhcpd.leases~
> write failed on etc/mtab : No space left on device
> rsync error: error in file IO (code 11) at receiver.c(243)
> rsync: connection unexpectedly closed (44803 bytes read so far)
> rsync: connection unexpectedly closed (44803 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(151)
> rsync: connection unexpectedly closed (76 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(151)
More information about the rsync
mailing list