rsync - Jun 2004 - [Bug 1442] rsync sender appears to hang when receiver recounters an error

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





------- Additional Comments From tom@hbsrx.com  2004-06-08 13:26 -------
Created an attachment (id=540)
 --> (https://bugzilla.samba.org/attachment.cgi?id=540&action=view)
strace of receiver process


-- 
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.

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





------- Additional Comments From wayned@samba.org  2004-06-08 14:37 -------
It's not a bug that the select() no longer includes the file descriptor for
reading the next message because rsync is busy trying to write the first message
over the socket to the sending (client) side.  As soon as that were to succeed,
it would read the next message.

So, the real question is, Why can't rsync send its message over the socket? 
Is
the remote-shell process hung?  What is happening on the sending side?

-- 
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.

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





------- Additional Comments From carson+samba@taltos.org  2004-06-08 19:02
-------
rsync will definitely hang in debug mode, because it tries to write more than
the TCP window before it is willing to read. The other side is doing the same
thing, so both block on writes in a deadly embrace. I doubt this is the cause
here, but the I/O loop needs to be fixed. A recent CVS commit may have improved
things, but I haven't looked at it.

-- 
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.

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





------- Additional Comments From Marc.Herbert@free.fr  2004-06-15 16:33 -------
I met a similar issue with rsync 2.6.2 at both ends.

Because of some silly partitioning mistake of mine, it took me very long to
realize that the destination disk was completely full. One thing is sure: rsync
did not help met _at all_ realize that. Instead of emitting some "disk
error/full" message as one could hope, it just silently _hung_ (both sender
and receiver sleeping on select().

As soon as some space was freed on the destination, everything was fine: I am
almost sure that small socket buffers and deadlocks were totally unrelated to my
"hanging rsync" problem. It seems to be only an issue of error
handling.



-- 
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.