cache_sync parse error: Unexpected object: integer about borg HOT 6 CLOSED

It seems that borg check --repair fixed the issue:

borg check --repair ssh://[email protected]:23/./borg/pegasus                                                              /usr/bin/borg:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  from pkg_resources import load_entry_point
This is a potentially dangerous function.
check --repair might lead to data loss (for kinds of corruption it is not
capable of dealing with). BE VERY CAREFUL!

Type 'YES' if you understand this and want to continue: YES
Enter passphrase for key ssh://[email protected]:23/./borg/pegasus: 
Unpacker crashed while unpacking item metadata, trying to resync... [chunk: 003515_7cddc8c390eb7ab3643fc106e4bf98efad5f3c26fbc4e0fc534efa0e8604d715]
5042 orphaned objects found!
Archive consistency check complete, problems found.

New backups are no longer failing.

Thanks for your help!

from borg.

Hmm, that code reads the archive metadata streams from the repo and rebuild the local chunkindex from that.

Looks like one archive (can be also a "hidden" .checkpoint archive) might be corrupt.

Guess I would do the following:

If you used borg < 1.2.5 for that repo follow the CVE-related steps from the top of the changelog (that is important in case you want to use borg check --repair later)

Then:

• borg list --consider-checkpoints REPO
• borg delete REPO::latest.checkpoint (you can also try adding 1 or 2 times --force and deleting the latest non-checkpoint archive, if you don't need it)

Does that fix it?

If not, run borg check --repair REPO.

from borg.

Thanks for the speedy response! :-)

The oldest archive in the repo is from Jan 2023, so the repo has been touched by a pre-1.2.5 version. The PPA I am using to install borg, does not yet prove 1.2.8, though. :-/

There is one .checkpoint archive. Is it safe to execute the steps you mentioned as long as I do not run borg check --repair before applying the steps from the changelog?

from borg.

Yes, as long as you don't run borg check --repair, it won't kill any archives with TAM issues.

For the CVE-related upgrade steps, make sure to read the docs for your borg version (e.g. the steps in the 1.2.8 docs won't work when using borg 1.2.7).

from borg.

I checked the current (1.2.7) source: yes, this seems the same issue (a corrupt archive) as described there:

#3454 (comment)

from borg.

Thanks! I applied the upgrade steps from the 1.2.7 changelog - the repo was't affected. Deleting the candidates of the affected archives did not work, currently running borg check --repair.

from borg.