[Borgbackup] Index object count mismatch, how to fix

Eric S. Johansson eric at in3x.io
Mon Aug 28 01:13:20 EDT 2017


I started getting backup outputs with cost exceptions and I thought I
just had another version mismatch. I upgraded both sides so they with
the same version of borg (1.0.11) on both sides and then ran a
repository check. I got the index object count mismatch error. I then
ran the same check on other archives I've made and they also have index
object count mismatches.

On my own personal archive I'm running check with the repair option and
I'm getting a lot of messages that say:

np1/pond/home/eric/windows-jun-25-2013.tar.gz: New missing file chunk
detected (Byte 66560501323-66562026633). Replacing with all-zero chunk.

I did a bit of googling and I turned up a bug report from about a year
ago which says the index mismatch is a nonissue and that he better
healing was implemented in item 1300. My interpretation of what I read
is that I need to do repair and then do a new backup in order to get rid
of the problems. Is that the right plan?  I'll make sure I do the right
recovery because I can accept toasting my own data but would really hate
to mess it up for anybody else.

--- eric

-- 

Eric S. Johansson
eric at in3x.io
http://www.in3x.io
978-512-0272




More information about the Borgbackup mailing list