Andrew Lentvorski wrote:
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.
I guess I need to add more background on the hardware involved: I am
trying to copy some data from an FC5 machine over NFS to an Infrant
ReadyNAS X6 running a Debian-based OS.
Update your rsync on *both* machines. Make sure the version numbers are
very close (identical ideally).
To this point I have assumed that the FC5 server is up to date (at least
as far as FC5 RPM's go).
I have no ability to update any apps on the ReadyNAS. Infrant has
promised shell access (SSH/SCP) later this year. I do know that the X6
is running a 2.4 kernel, if that matters. I'm also pretty sure that its
version of NFS is <= v3.
Is this filesystem active? If the file is changing out from under cp or
rsync that will often confuse them.
The FC5 file system is active - but no more so than the average home LAN
fileserver (which is what it is). The ReadyNAS is intended to eventually
replace the FC5 box - once it tests out okay. I plan at least a three
month overlap period before taking down the FC5 box.
To be more precise, the files and dirs on which it seems to hang are
basically archival and not in current active use.
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.
I guess that begs the definition of "cheap". I have tried both a Netgear
FVS-318v3 and Linksys RV082 router/firewalls. If you mean "Consumer
grade", then yeah, cheap.
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
Unfortunately, as explained above, SCP is not yet an option. I do have
the options of using either FTP or HTTP(S), but I want to work on one
problem at a time (NFS), and anyway I'm not too keen on using those
protocols at the present.
I have the existing (FC5) fileserver available to remote family members
via VPN's (SSH/SCP - NFS/Samba), and via 'Net access using SSH/SCP.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
