You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part 2: wbe-tp saves lock/e623a33a, sees lock/f813ae713d when listing locks, but can not access it when calling GET /lock/lock-id
since it has already been deleted by wbe-pc.
I think this problem might be addressed if there is no retry when Load() fails with noExistError.
I might be overlooking other factors. I would appericiate if anyone could tell me if this makes sense or point me in the right direction.
Did restic help you today? Did it make you happy in any way?
Despite this cahllenge, restic is what got me to try and setup proper backups on all my devices again. Overall, it has been way more fun than frustration compared to other solutions I've tried in the past. Thank you.
Output of
restic version
Two devices
wbe-pc: restic 0.16.0 compiled with go1.20.8 on linux/amd64
wbe-tp: restic 0.16.0 compiled with go1.20.8 on linux/amd64
How did you run restic exactly?
same commands were run on both devices
What backend/server/service did you use to store the repository?
Cloudflare R2 configured with rclone
Expected behavior
Expected all restic commands on both devices to either acquire lock and complete or fail.
Actual behavior
restic continues retrying to load a lock file that no longer exists.
Steps to reproduce the behavior
I am able to reproduce the problem by running the above commands in "how did you run restic" section.
But this problem will not happen every time.
Do you have any idea what may have caused this?
A lock file that exists when restic calls GET /locks/ but is deleted before restic calls /locks/lock-id.
Logs and trace are attached at the end.
Some relevant parts of the logs are included here.
Part 1: wbe-pc saves lock/f813ae713d, does backup, deletes lock
Part 1 log
Part 2: wbe-tp saves lock/e623a33a, sees lock/f813ae713d when listing locks, but can not access it when calling GET /lock/lock-id
since it has already been deleted by wbe-pc.
Part 2 log
Part 3: wbe-pc starts second restic command but since wbe-tp has not removed lock/e623a33a, the command will eventually fail out.
Part 3 log
Do you have an idea how to solve the issue?
I think this problem might be addressed if there is no retry when Load() fails with noExistError.
I might be overlooking other factors. I would appericiate if anyone could tell me if this makes sense or point me in the right direction.
Did restic help you today? Did it make you happy in any way?
Despite this cahllenge, restic is what got me to try and setup proper backups on all my devices again. Overall, it has been way more fun than frustration compared to other solutions I've tried in the past. Thank you.
Logs
restic-trace.txt
restic-debug-wbe-tp.log
restic-debug-wbe-pc.log
The text was updated successfully, but these errors were encountered: