Unable to create lock in backend


#1

Hello

Currently using Restic to backup to my Backblaze b2 accounts. Seems to work for the most part and the data is uploaded, however I always seem to get stuck on the locks

scan [/home/paths/to/back/up]
scanned 125321 directories, 242021 files in 10:10
[17:08] 100.00%  41.579 MiB/s  41.741 GiB / 41.599 GiB  367719 / 367342 items  0 errors  ETA 0:00 
duration: 17:08, 41.43MiB/s
snapshot 524a328d saved
unable to create lock in backend: repository is already locked by PID 5666 on ubuntu by root (UID 0, GID 0)
lock was created at 2018-02-08 01:10:58 (255h42m35.442540183s ago)
storage ID 87a257c8
unable to create lock in backend: repository is already locked by PID 5666 on ubuntu by root (UID 0, GID 0)
lock was created at 2018-02-08 01:10:58 (255h42m49.135698648s ago)
storage ID 87a257c8
unable to create lock in backend: repository is already locked by PID 5666 on ubuntu by root (UID 0, GID 0)
lock was created at 2018-02-08 01:10:58 (255h42m53.85260751s ago)

I used the unlock command to unlock the repo. The unlock is reported as sucessful. I run the backup again and it just hangs once the snapshot has been created

7:53] 100.00%  91.611 MiB/s  42.316 GiB / 42.299 GiB  372282 / 37... ETA 0:00 
duration: 7:53, 91.47MiB/s
snapshot 540e9f5d saved
...

Any help would be great

Thanks


#2

You can run restic unlock to remove the locks.
BTW: There is a brand new version of restic you should check out if you are using B2 as your backend.

Link: https://github.com/restic/restic/releases/tag/v0.8.2


#3

Hey, thanks for the report. I’m pretty sure this is a bug, would you mind creating a issue and filling out the template? Then we can track it and have an in-depth look.

Is this bug reproducible? Does it happen every time?


#4

Hey, yep, ive been able to reprocuduce it on my machine

issue #1627


#5

We solved it (at least I think we solved it), it was a bug in a script.


#6

7 posts were split to a new topic: Repository is already locked