DJA wrote:
I tried this, but got this error after a while:
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe
(32)
rsync: close failed on "/eighthome/dallen/Application Data/Spybot -
Search & Destroy/Recovery/.Mozilla.zip.TI4SDn": Input/output error (5)
rsync error: error in file IO (code 11) at receiver.c(628) [receiver=2.6.8]
rsync: connection unexpectedly closed (14802 bytes received so far)
[sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
[sender=2.6.8]
As you might guess the file mentioned above is a Windows file. I was
getting similar I/O errors using a cp -av command also, although it
wasn't on the same file.
Anyone see this kind of error before with rsync?
Well, I have seen something similar. However, it was a couple versions
ago and I was trying to transfer to Solaris. There were endianness
problems.
Update your rsync on *both* machines. Make sure the version numbers are
very close (identical ideally).
Is this filesystem active? If the file is changing out from under cp or
rsync that will often confuse them.
Do you have some cheap router/firewall in between them? One of the
standard problems with torrent files is that occasionally a router will
rewrite a chunk of bytes that it thinks is an IP address but is actually
data. Very annoying.
When I have true problems transferring data, I pack things up into a
tarfile and use scp.
Although, rsync really has been pretty good lately.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
