[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] corrupted files in destination while source is

From: Joe Steele
Subject: Re: [rdiff-backup-users] corrupted files in destination while source is good and no errors when running rdiff-backup
Date: Thu, 16 Mar 2017 14:12:15 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

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):


The bug can generate the type of errors shown in your verify log.

See if your version of rdiff-backup includes the patches attached to the bug report. If not, apply the patches and see if that fixes any of your problems.


On 3/16/2017 9:43 AM, Jelle de Jong wrote:
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
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

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

After some investigating --verify outputs the bad documents:


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

rdiff-backup-users mailing list at address@hidden
Wiki URL:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]