From charlesreid1

No edit summary
No edit summary
Line 18: Line 18:
     incremental scan that uses much less memory than before and begins the transfer after the scanning of the first few directories have been completed. This incremental scan only affects our recursion algorithm, and does not change a non-recursive transfer. It is also only possible when both ends of the transfer are at least version 3.0.0.  
     incremental scan that uses much less memory than before and begins the transfer after the scanning of the first few directories have been completed. This incremental scan only affects our recursion algorithm, and does not change a non-recursive transfer. It is also only possible when both ends of the transfer are at least version 3.0.0.  
</pre>
</pre>
http://rsync.samba.org/ftp/rsync/

Revision as of 18:48, 11 July 2011

This problem is likely due to lack of memory [1]:

Received disconnect from 155.97.192.16: 2: Corrupted MAC on input.
rsync: writefd_unbuffered failed to write 32768 bytes [sender]: Broken pipe (32)
rsync: connection unexpectedly closed (8874 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(453) [sender=2.6.9]

Here [2] someone says you should see it say that it is incrementally updating files

but here [3] it says that that only happens with rsync version 3+

-r, --recursive
    This tells rsync to copy directories recursively. See also --dirs (-d). 
Beginning with rsync 3.0.0, the recursive algorithm used is now an
    incremental scan that uses much less memory than before and begins the transfer after the scanning of the first few directories have been completed. This incremental scan only affects our recursion algorithm, and does not change a non-recursive transfer. It is also only possible when both ends of the transfer are at least version 3.0.0. 


http://rsync.samba.org/ftp/rsync/