On Sun, Aug 12, 2012 at 11:41 AM, Linda Walsh rs...@tlinx.org wrote:
How can I show it to you?
One thing you can try is to build 3.1.0dev (from git or nightly tar file)
and run that with --debug=hlink5. If the copying is remote (using ssh),
you can put the executable off to the side somewhere
On Sun, Aug 5, 2012 at 1:50 AM, Linda Walsh rs...@tlinx.org wrote:
How can I have a proto incompat when it it is talking to itself?...
You cited a hard-link bug in the incremental recursion algorithm. You can
work around it by specifying --no-inc-recursive (--no-i-r). If you have a
How can I show it to you? I'm pretty sure I can produce it on demand -- just
take another snapshot and do a rsync w/o the no-i-r switch...
But it's not like I can send you a HD via email...they are sorta big...?
Wayne Davison wrote:
On Sun, Aug 5, 2012 at 1:50 AM, Linda Walsh
Familiar? protocol error on a local file copy?
How can I have a proto incompat when it it is talking to itself?...
This was on the ERROUT...
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]:
Broken pipe (32)
File-list index 531530 not in 531937 - 533437
