3.1.1 on both sides: it says fixed by upgrade. I found a way to upgrade. Using: rsync version 3.1.1 protocol version 31 on receiving side that issues the rsync command, and rsync version 3.1.1 protocol version 31 on the remote sending side. Im still getting the same thing: rsync: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed. this is rsync from debian jessie 3.1.1-3 (/var/lib/apt/lists/ftp.ca.debian.org_debian_dists_jessie_main_binary-amd64_Packages) (/var/lib/dpkg/status)
Hello, recently we triggered this very same bug. I found a simple method of reproducing the bug: $ mkdir newdir; cd newdir $ mkdir -p base base/sub overlay tgt $ touch {base,overlay}/foo $ ln base/foo base/sub/foo $ rsync -avH overlay/ base/ tgt sync: hlink.c:129: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed. rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(228) [sender=3.2.5] kind regards, Dick Snippe
Ah, forgot to notice thats we can reproduce this on rsynv version 3.2.5 and 3.4.1; I'm guessing it can be reproduced on many other rsync versions.