On Thu, 16 Dec 2004 14:21, Jon Nelson wrote:
On Wed, 15 Dec 2004, Paul W. Abrahams wrote:
pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515)
pwa@suillus:~>
I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images.
Basically, the only time I've ever seen that is when rsync gets "confused", which is *quite* rare. I *have* seen it happen, although that was quite some time ago.
The following appeared on a local LUG list which may shed some light on the problem. I have not encountered the problem myself, but then again I don't use rsync that often. ------------------------------------------ ------------------------------
I'm using --bwlimit because I have found that rsync hangs if I don't. I have no idea why. I've been slowly increasing --bwlimit to find out if there is a critical point.
There's a good idea I didn't think of. I've had this happen too and to put it bluntly "It's not rsync's fault the network can't handle the full bandwidth." - usually the receiver's network card driver or stack can't keep up, you'll probably find it works fine without the limit for good network cards with big buffers & DMA - try the opposite direction just as an experiment if you have a variety of NICs. ----------------------------------------- -------------------------------- -- Regards, Graham Smith ---------------------------------------------------------