[Borgbackup] borg failed integrity check

[Neal Becker]

Well I rm'd .cache/borg on the client, and reran backup successfully

On Thu, Nov 16, 2017 at 8:24 AM Thomas Waldmann <tw at waldmann-edv.de> wrote:

> Hi Neal,
>
> > The borg versions may have been switched back and forth a between 1.0.?>
> and 1.1.12 because 1) the versions on f26 and f27 are different
>
> So it is 1.0.x and 1.1.2.
>
> > Cache integrity data not available: old Borg version modified the cache.
> This is expected when switching between 1.0 to 1.1 and no problem, just
> a notice.
>
> > Keeping archive: nbecker2-2017-11-15                  Wed, 2017-11-15
>
> OK, so your script runs prune first and then create.
>
> > File failed integrity check:
> >
> /home/nbecker/.cache/borg/234c85641ffd393726ad1d0e3adadf78315db6e53725a167bd1cebb7c99ea19f/files
>
> OK, so it thinks the "files" cache is (was) corrupted for that repo.
>
> If you start borg create again, do you get same error?
>
> If you do, what is ls -l
>
> /home/nbecker/.cache/borg/234c85641ffd393726ad1d0e3adadf78315db6e53725a167bd1cebb7c99ea19f/files
> ?
>
> Do you always run borg as the same user?
>
> > line 910, in file_known_and_unchanged
> >    self._read_files()
>
> OK, so this is borg create demand-loading the files cache - and it is
> raising IntegrityError because the hash does not match the files content
> read from disk.
>
> There could be different reasons for this:
>
> - you discovered a bug (possible, but not extremely likely as you are
> the first reporting this but not the first using 1.1.2)
>
> - the "files" cache on disk was somehow corrupted (content modified,
> truncated / appended, whatever), so it does not match the stored hash
> any more
>
> - the hash was corrupted
>
> Corruption could be due to:
> - disk errors
> - transmission errors
> - RAM errors
>
> The FAQ has some hints about checking your hardware.
>
> The hash we use is a strong hash, so it could even be it detects errors
> that have otherwise not been detected by weaker mechanisms.
>
>
> Cheers, Thomas
>
> --
>
> GPG ID: 9F88FB52FAF7B393
> GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20171116/16fda46c/attachment-0001.html>