Borg: Failed to create/acquire the lock ...8ee53ed8/lock.exclusive

Created on 15 Mar 2017 · 6Comments · Source: borgbackup/borg

i have a system which often reboots/crashes (due to power loss) and 3 of 5 backups weren't working yesterday, and the logs show:

Failed to create/acquire the lock /backup/nixcloud-backup/.borg-cache/e4f72857fd062fadead393dd604d052d018ba6e3f115fb23f3bf7dcd8ee53ed8/lock.exclusive (timeout).
borg error, exiting

can removal of these files be automated? one could write the PID into the lockfile somewhere and check if the process is still around.

Source

qknight

Most helpful comment

I believe you need borg break-lock

Abogical on 15 Mar 2017

👍3

All 6 comments

I believe you need borg break-lock

Abogical on 15 Mar 2017

👍3

can removal of these files be automated? one could write the PID into the lockfile somewhere and check if the process is still around.

that feature is in beta

enkore on 15 Mar 2017

@enkore: any pointers? i need that, too...

rpodgorny on 20 Mar 2017

@rpodgorny maybe wait until 1.1.0b4 gets released. only for testing yet, don't use it for important data.

ThomasWaldmann on 20 Mar 2017

In 1.1.0b3:

automatically remove stale locks - set BORG_HOSTNAME_IS_UNIQUE env var to enable stale lock killing. If set, stale locks in both cache and repository are deleted. #562 #1253

FabioPedretti on 20 Mar 2017

one could write the PID into the lockfile somewhere and check if the process is still around.

Actually I wrote a script to do something like that locally. I think this is a nice and reliable workaround. See https://github.com/rugk/borg-cron-helper