-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Remove(<lock/5a53798b51>) returned error #2452
Description
Output of restic version
restic 0.9.4 compiled with go1.11.6 on linux/amd64
How did you run restic exactly?
Via a script that passes arguments to restic.
restic backup --repo b2:${bucket} $(awk 'BEGIN{ ORS=" " }{ print }' "${includeList}") --verbose=2 \
--password-file=<(decrypt "${bucket}" | sed -n 3p) -o b2.connections=100
What backend/server/service did you use to store the repository?
Backblaze B2
Expected behavior
Not receiving lock errors.
Actual behavior
Remove(<lock/5a53798b51>) returned error, retrying after 3.588215337s: Delete: b2_download_file_by_name: 404: bucket [bucket] does not have file: locks/5a53798b511f2fe2e7b31d98bf507834270dad5974b365f3dd9db8a19a70b3be
unable to refresh lock: Delete: b2_download_file_by_name: 404: bucket [bucket] does not have file: locks/5a53798b511f2fe2e7b31d98bf507834270dad5974b365f3dd9db8a19a70b3be
I am getting the above errors when attempting to run a backup. This is the first time I've seen these errors occur and there are many of them. The errors only occur on one b2 bucket, the other buckets are fine. The script runs an unlock command on the repo before backing up, and the errors are still present after doing an unlock and prune manually. All the data appears to have been backed up successfully, and this is the first time I've seen this in over a year of using Restic.
Steps to reproduce the behavior
Run a backup or prune.
Do you have any idea what may have caused this?
Nope
Do you have an idea how to solve the issue?
Possibly delete the files from the repo and reupload, however due to the large about of data this is not desirable.