Output of restic version
restic 0.17.0 compiled with go1.22.5 on linux/amd64
What backend/service did you use to store the repository?
Backblaze B2
Problem description / Steps to reproduce
Hi,
We upload lots of large files to B2 on a nightly basis. Since upgrading to 0.17.0 on Debian, we're seeing occasional errors uploading to B2:
unable to create lock in backend: circuit breaker open for file <lock/c498f551d0>
bytes to write=10240, bytes written=4096, total written 60K
buffer (writer): write of data failed: Success
Unable to write to output file ()
We pipe tarballs into restic using the following command inside a script:
... | restic backup --quiet --stdin --stdin-filename "${TARBALL}.tar" -o b2.connections=8
If we set RESTIC_FEATURES=backend-error-redesign=false as mentioned in another issue then we don't see this issue - uploads happen reliably again.
Expected behavior
Upload to B2 reliably
Actual behavior
As described above,
Do you have any idea what may have caused this?
Given that setting RESTIC_FEATURES=backend-error-redesign=false works around this issue, it's likely to be something in that redesign.
Did restic help you today? Did it make you happy in any way?
Restic is a handy part of our backup regime, and has been reliable and straightforward to use. Thank you!
Output of
restic versionrestic 0.17.0 compiled with go1.22.5 on linux/amd64
What backend/service did you use to store the repository?
Backblaze B2
Problem description / Steps to reproduce
Hi,
We upload lots of large files to B2 on a nightly basis. Since upgrading to 0.17.0 on Debian, we're seeing occasional errors uploading to B2:
We pipe tarballs into restic using the following command inside a script:
... | restic backup --quiet --stdin --stdin-filename "${TARBALL}.tar" -o b2.connections=8If we set
RESTIC_FEATURES=backend-error-redesign=falseas mentioned in another issue then we don't see this issue - uploads happen reliably again.Expected behavior
Upload to B2 reliably
Actual behavior
As described above,
Do you have any idea what may have caused this?
Given that setting
RESTIC_FEATURES=backend-error-redesign=falseworks around this issue, it's likely to be something in that redesign.Did restic help you today? Did it make you happy in any way?
Restic is a handy part of our backup regime, and has been reliable and straightforward to use. Thank you!