[Bug 5478] rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=5478

--- Comment #17 from Eric Shubert <ejs at shubes.net> 2011-09-29 17:16:38 UTC ---
(In reply to comment #16)
> 
> So now I'm beginning to think that the problem is (indeed) outside of the rsync
> code. I've examined the 2 target hosts (one that worked and one that doesn't),
> and tried to determine "what's different?". These hosts are all VMs that are
> running under VMware Server2. The host that worked is running CentOS 5.6, while
> the one that's failing is running CentOS 5.4 (450 days uptime). I'm going to
> upgrade the failing host OS to CentOS 5.7 and see if that changes anything. I
> know that some versions of glibc (> 2.5-34, < 2.5.58) had mysterious problems
> with VMware Server 2 (guests terminating for no apparent reason). I'm wondering
> if there's something else in glibc that's perhaps having a problem with VMware
> Server 2. (I realize that Server 2 is essentially dead and will be migrating to
> KVM in the near future, although Server2 has been quite stable for me.)
> 

I've upgrade the target host, and still no dice. Same failure. It seems odd to
me that the transmission fails at different points in the process, anywhere
from 3.5 minutes to 14.75 minutes.

I'm presently thinking that the problem is not with rsync itself, but with some
aspect of the network connection. I'm seeing no corresponding ethernet errors
on either end though, and the network seems to be fine otherwise.

I'd have to say at this point that the failures appear to be happening only
with large files.

I could sure use some pointers with identifying what the cause of this failure
is. I have a test file that fails regularly (if not consistently), and should
be able to tell easily when it's fixed.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.