DO NOT REPLY [Bug 6175] write last transfer status when timeout or other error happens
samba-bugs at samba.org
samba-bugs at samba.org
Tue Oct 26 23:30:54 MDT 2010
https://bugzilla.samba.org/show_bug.cgi?id=6175
tim.liim at alcatel-lucent.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tim.liim at alcatel-lucent.com
------- Comment #5 from tim.liim at alcatel-lucent.com 2010-10-27 00:30 CST -------
These bugs seem to be related (having similar error messages:
connection unexpectedly closed, broken pipe, timeout).
bug7757
with big file, rsync times out out when it should not; the
sender is still responsive
bug2783
Random high loads during syncs (server side) / client stream errors
rsync: connection unexpectedly closed (2761332 bytes received so far)
[generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(365)
bug5478
rsync: writefd_unbuffered failed to write 4092 bytes [sender]:
Broken pipe (32)
rsync: writefd_unbuffered failed to write 4092 bytes [sender]:
Broken pipe (32)
io timeout after 30 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(239)
[sender=3.0.2]
bug5695
improve keep-alive code to handle long-running directory scans
./io.c:void maybe_send_keepalive(void)
bug6175
write last transfer status when timeout or other error happens
rsync: writefd_unbuffered failed to write 4 bytes [sender]:
Broken pipe (32)
rsync: connection unexpectedly closed (99113 bytes received so
far) [sender]
rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.5]
bug7195
timeout reached while sending checksums for very large files
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the rsync
mailing list