Re: [rdiff-backup-users] Re: Too many recent increments

[Jon Dye]

2009/5/7 Maarten Bezemer <address@hidden>:
>
> On Thu, 7 May 2009, Jon Dye wrote:
>
>>> I've been using rdiff-backup for 6 months or so with no problems but
>>> recently my backup is failing with the error "AssertionError: Too many
>>> recent increments".
>>>
>>> I get this error whether I'm doing a backup or --check-destination-dir.
>
> Skimming over the sources, this error suggests that, while trying to remove
> an increment, it found more than one. I guess that could mean it found an
> increment file without the corresponding mirror_metadata tree.
> If that's true, you most likely have a corrupted backup tree and continuing
> to use it would not be very wise. (Meaning: you can use the current state as
> a basis to start a new tree, loosing the history).
>
> Could you run rdiff-backup --check-destination-dir with a higher verbosity
> level (say -v7) and paste the entire output, including a couple of lines
> before the backtrace starts? That could point us to one specific location
> and might help with 'fixing' the problem.

Output attached.

Interestingly it mentions 9th March but my backup directory has:
-rw------- 1 jon users      10 2009-03-09 07:26
current_mirror.2009-03-09T07:21:17Z.data
-rw------- 1 jon users      10 2009-03-26 06:43
current_mirror.2009-03-26T06:38:19Z.data

and increments up to 26th March.

JD

rdiff-backup.log
Description: Binary data