[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

Scott Wood <woodystrash at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |woodystrash at hotmail.com

--- Comment #28 from Scott Wood <woodystrash at hotmail.com> 2013-05-22 03:43:41 UTC ---
I believe I am a recent victim of this bug.  I am doing an rsync via ssh of
large files (from 4GB, up to a couple hundred GB).  I have the -W and have
disabled compression on the file type that is failing most often.

Here is a rough example of the rsync push command:

rsync -avW --timeout=0 --rsync-path='/bin/rsync_3.0.9' --skip-compress=ext -e
"ssh -c arcfour -i /home/user/.ssh/CUSTOM_id_rsa" /path/to/bigfile.ext
remoteuser at theserver:/path/to/destination

And the connection is terminated with an ACK,RST packet from the server
resulting in the following on the client:

Read from remote host theserver: Connection reset by peer
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken
pipe (32)
rsync: connection unexpectedly closed (28 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]

I have reproduced the result with a multitude of versions, including 3.0.4,
3.0.7 and 3.0.9 on the client side, and 3.04 and 3.09 on the server side.  I
have the following questions:

1) Chip Scwheiss, re: comment 23.  Do you have a RHEL bug reference so I can
see if this is resolved, or pursue it further with them under our support
contract?
2) What is the consensus on the security implications and effectiveness of
Chip's iptables suggestion?
3) If it boils down to needing to --bwlimit, does anyone have any suggestions
other than trial and error to calculate the maximum it should be able to
handle? As we have many TB to move, this would not be the ideal solution.

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