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

Hello, I'm compare the files. The files create by rdiff-backup has the right size, but it filled with zeros. So know the question remain. Why is rdiff-backup is creating a file with only zeros. -- Patrik Dufresne On Tue, Mar 21, 2017 at 9:27 AM, Jelle de Jong wrote:

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

root@backup:~# md5sum /srv/storage/backups/libvirt-filesystems/sr7-sdb2//DSC_1319.JPG 8cbb1482783c05a1604987532bdc6540 /srv/storage/backups/libvirt-filesystems/sr7-sdb2//DSC_1319.JPG root@backup:~# md5sum /mnt/sr7-sdb2//DSC_1319.JPG 913ee9c4832f69cc60a99dbc7b9e57c9 /mnt/sr7-sdb2//DSC_1319.JPG

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

The files where no hard links, on the ntfs source directory they show up as real files. Kind regards, Jelle de Jong On 16/03/17 19:12, Joe Steele wrote: This is just a guess, but if your de-duplication process involves the use of hard links which rdiff-backup is backing up, then your

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

This is just a guess, but if your de-duplication process involves the use of hard links which rdiff-backup is backing up, then your problem may relate to the following bug (which affects hard links): http://savannah.nongnu.org/bugs/?26848 The bug can generate the type of errors shown in your