Hi,
I can say that this problem persists in Stretch. I also went to copy a lot of files to another machine, then went away, and found that rsync was happily claiming to have written files correctly (I used -azvvcP), but the target directory was empty. This was with rsync 3.1.2-1 on amd64 on the sender side (Stretch), and rsync 3.1.1-3 amd64 on the receiver side (Jessie). I have ext4 file systems on both sides of the copy operation. I think this bug should be upgraded to 'serious', since it could easily result in data loss if the sender would delete files after transfer on the sendind side. Cheers, --Toni++
