DO NOT REPLY [Bug 5727] rsync crashes while copying large directory.

[samba-bugs at samba.org]

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


wayned at samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Comment #4 from wayned at samba.org  2008-08-31 13:16 CST -------
This error:

"invalid message 101:7104843 [sender]"

Indicates that this byte sequence that was received:

0x4b 0x69 0x6c 0x6c 

Which is the ASCII string "Kill".  So, it looks like your shell likes to send
extra text on stdout if something is killed ("Killed 1234" or some such).

If you haven't done so already, you should investigate what is killing the
remote process (e.g. an out-of-memory error).

"However this doesn't mean that the bug has been fixed. It means it's harder to
trigger."

That's all that we can hope for with respect to to memory issues.  With the way
rsync works, it is pretty near the limit of what memory reduction is possible,
and incremental recursion is already a huge gain for transferring larger sets
of files than ever before.  Changing rsync to not cache all the files in a
directory would be radical surgery, and is not going to happen in this
codebase.

One thing that can make a difference with regard to memory issues is the alloc
library that is used.  There are some malloc libraries that will gradually lose
memory if they don't do a good job of re-using freed memory.  There was a
recent report by a user that switching their malloc library made rsync's
incremental recursion work for them.  (If you're using glibc, this is probably
not your problem, though.)


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