restic forget is failing because of stale locks. Running
restic unlock before running
restic forget gives this output:
repository <repo> opened successfully, password is correct successfully removed locks repository <repo> opened successfully, password is correct unable to create lock in backend: repository is already locked by PID <pid> on <machine> by root (UID 0, GID 0) lock was created at 2021-07-05 01:39:15 (758h5m55.133873493s ago) storage ID <storageid> the `unlock` command can be used to remove stale locks
The repo is an s3 instance at Storj.io.