[rdiff-backup-users] corrupted files in destination while source is good and no errors when running rdiff-backup

[Jelle de Jong]

Hello everybody,

Thank you for rdiff-backup it has been very useful for me for many years.

I am making a new solution to be able to use rdiff-backup with ntfs3 
with a new dedup plugin, this seem to be working now.

I ran rdiff-backup on the same volume, some of these runs have been done 
on currupt files while fine tuning the de-duplication read plugin.

address@hidden:~# rdiff-backup --list-increments 
/srv/storage/backups/libvirt-filesystems/sr7-sdb2/
Found 9 increments:
    increments.2017-02-09T18:52:53+01:00.dir   Thu Feb  9 18:52:53 2017
    increments.2017-02-12T03:57:18+01:00.dir   Sun Feb 12 03:57:18 2017
    increments.2017-02-24T12:42:23+01:00.dir   Fri Feb 24 12:42:23 2017
    increments.2017-02-27T13:45:11+01:00.dir   Mon Feb 27 13:45:11 2017
    increments.2017-02-27T17:03:21+01:00.dir   Mon Feb 27 17:03:21 2017
    increments.2017-02-28T14:56:43+01:00.dir   Tue Feb 28 14:56:43 2017
    increments.2017-03-05T04:40:29+01:00.dir   Sun Mar  5 04:40:29 2017
    increments.2017-03-09T19:24:12+01:00.dir   Thu Mar  9 19:24:12 2017
    increments.2017-03-12T03:30:37+01:00.dir   Sun Mar 12 03:30:37 2017
Current mirror: Tue Mar 14 19:26:57 2017

We fixed all the errors and I can read all the documents from the source 
directory fine , but rdiff is having corrupt documents in the backup 
destination.

When testing I found documents with different md5sums in my backup and 
the source destination.

After some investigating --verify outputs the bad documents:

http://paste.debian.net/hidden/d311cfcf/

Why is rdiff-backup running fine over the directory but still has 
corrupted documents in the destination and how do I fix this without 
removing the full backup.

Kind regards,

Jelle de Jong