First post, done some due diligence and can’t seem to find an easy solution.
I’m an idiot and I left a repository (Backblaze B2 backend) fuse-mounted on a machine for a very long time.
restic check tells me that the repo is mounted on a machine:
# restic check using temporary cache in /tmp/restic-check-cache-629967059 repository e4de1ac5 opened successfully, password is correct created new cache in /tmp/restic-check-cache-629967059 create exclusive lock for repository Fatal: unable to create lock in backend: repository is already locked by PID 4168 on DBLIVE01 by root (UID 0, GID 0) lock was created at 2019-09-26 22:18:42 (3689h46m57.965138513s ago) storage ID 4f769b1c
Hey! Only five months or so The PID that it mentions is long gone, perhps due to some troubleshooting I’ve been doing. I noticed this on another box and duly ran
restic unlock --remove-all, which worked (and saved my bacon), however on this one it just hangs with no further info, even if verbose flags are set:
# restic -vvv unlock --remove-all repository e4de1ac5 opened successfully, password is correct
Is there any way out of this? Any way to get more info about what may be happening?
Thanks in advance…