Possible unlock bug?

So as a test, I ran restic unlock while an unimportant backup was running. From what I read in the forum, restic isn’t supposed to remove active locks. I saw the lock file in the repo, and it was less than 4m old. Why would it have been removed? (I obviously didn’t use the --remove-all switch.)

The backup is repeatedly complaining that the lock doesn’t exist, as well.

I’m on v0.9.5-31-g3ca42405 if that matters.

1 Like