[rdiff-backup-users] Also get bad index order assertion when recovering from failed backup

[JoSH Lehan]

I'll also need to be added to the list of users who have been bitten
by the "Bad index order" assertion.

The scenario:

Initial backup successful.

Incremental backups successful.

Many more incremental backups successful.

However, the most recent incremental backup didn't finish, for
unrelated reasons.

That failed backup changed enough of the rdiff-backup data store to
"dirty" it.  Additional attempts at applying an incremental backup now
fail, with an error message telling the user to please run the
--check-destination-dir command on the rdiff-backup data store.

So, I am trying to rollback the rdiff-backup data store, by doing just
that.  I'm using the --check-destination-dir command, as follows:

rdiff-backup --check-destination-dir /my/backup/directory

Unfortunately, I get the "Bad index order" assertion.  It's in exactly
the same place as the others who have previously posted to this
mailing list.

The FAQ has some helpful ideas, but they don't apply in this
situation.  The problem did not happen when trying to do a backup.
Instead, the problem happened when running the --check-destination-dir
command, on an already-existing rdiff-backup data store.

http://www.nongnu.org/rdiff-backup/FAQ.html#badindex

Has anybody made any progress on solving this issue?  This is a rather
important problem, I would think, as it renders the data store
unusable.  No backups or restores can be made from it.

Thanks!

Josh