locking related KeyError exception on every command about borg HOT 8 CLOSED

1.2.0 is rather old meanwhile, you could try a much more recent borg 1.2.x with quite some bug fixes and also a few new features from the maintainer's ppa:

https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup?field.series_filter=jammy

Alternatively, you could try:

• make very sure no borg is (going to be) active in that repo, then use: borg break-lock REPO
• if that doesn't fix it, again make very sure no borg is (going to be) active in that repo and manually remove files/dirs with "lock" in the name from the repo directory.

from borg.

borg break-lock REPO seems to be the only borg command that does not produce the error. Unfortunately, it doesn't help.

Even after rm -r REPO/lock* I receive the same errors upon trying any borg command.

from borg.

The issue does not reproduce on 1.2.7.

It is unfortunate that Ubuntu LTS has a buggy version.

from borg.

If 1.2.0 still crashes: can you do a ls -l REPO_DIR?

from borg.

Debian/Ubuntu policy is to usually not do version upgrades of packages in a stable release, but only patch security or other severe bugs.

from borg.

BTW, if you upgrade to > 1.2.4, read the changelog, esp. the required migration steps at top of the changelog.

from borg.

If 1.2.0 still crashes: can you do a ls -l REPO_DIR?

1.2.0 does still crash. Here's a ls -l after a couple of runs:

итого 29628
-rw-------  1 eugenschmidt eugenschmidt      700 апр  1 17:44  config
drwxrwxr-x 17 eugenschmidt eugenschmidt     4096 мар 27 14:25  data
-rw-------  1 eugenschmidt eugenschmidt     2518 апр  1 19:22  hints.14387
-rw-------  1 eugenschmidt eugenschmidt 30304298 апр  1 19:22  index.14387
-rw-------  1 eugenschmidt eugenschmidt      190 апр  1 19:22  integrity.14387
-rw-------  1 eugenschmidt eugenschmidt       62 апр  1 19:21 'lock (2).roster'
-rw-------  1 eugenschmidt eugenschmidt       62 апр  1 19:22 'lock (3).roster'
-rw-------  1 eugenschmidt eugenschmidt       16 апр  1 19:22  nonce
-rw-rw-r--  1 eugenschmidt eugenschmidt       73 янв 15 13:09  README

BTW, if you upgrade to > 1.2.4, read the changelog, esp. the required migration steps at top of the changelog.

I have checked the changelog on the official site, and it doesn't seem to list any breaking changes and/or upgrade notes between 1.2.0 and 1.2.7. Fortunately, simply upgrading the package and running the same commands produces no errors and seems to work fine.

from borg.

Remove these lock*.roster files while borg is not active.

And read the top of the changelog "important notes" (again) if you do not want to risk data loss. If you read it on the web, choose the correct borg version using the version selector at the lower right.

https://borgbackup.readthedocs.io/en/1.2.7/changes.html#pre-1-2-5-archives-spoofing-vulnerability-cve-2023-36811

from borg.