[Borgbackup] what do I do with inconsistencies?

[Adrian Klaver]

On 06/15/2016 11:48 PM, Thorsten von Eicken wrote:
> This is a pretty new repository with just a couple of archives and I'm
> having consistency issues that don't seem to get repaired:
>
> == Starting backup for repo home at 2016-06-15T09:49-0700
> Archive: backup at backup:/big/h/home::home-2016-06-15T09:49-0700
> borg create --show-rc -s -e .cache -C lzma
> backup at backup:/big/h/home::home-2016-06-15T09:49-0700 /big/home /etc
> /root /big/usr-local
> == Starting check for repo home
> Repository: backup at backup:/big/h/home
> borg check --show-rc --last 3 backup at backup:/big/h/home
> borg.repository Remote: Index object count mismatch. 549207 != 549310
> borg.repository Remote: Completed repository check, errors found.
> terminating with warning status, rc 1
>
> and later I tried to repair it:
>
> root at h /b/h/tve# borg check --show-rc --repair backup at backup:/big/h/home
> 'check --repair' is an experimental feature that might result in data loss.
> Type 'YES' if you understand this and want to continue: YES
> 103 orphaned objects found!
> Archive consistency check complete, problems found.
> root at h /b/h/tve# borg check --show-rc --repair backup at backup:/big/h/home
> 'check --repair' is an experimental feature that might result in data loss.
> Type 'YES' if you understand this and want to continue: YES
> 1 orphaned objects found!
> Archive consistency check complete, problems found.
>
> Suggestions?

I do not know the answer, but I do have some questions:

What version of Borg?

What are the OSes and file systems involved?

What is the history of the repo?
In other words have you changed the Borg version that was backing up to it?

Have there been any incomplete/disconnected create runs?

After your last repair what does check show without --repair?

>
>
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>


-- 
Adrian Klaver
adrian.klaver at aklaver.com