forked from TrueCloudLab/restic
d05f6211d1
restic must be able to refresh lock files in time. However, large uploads over slow connections can cause the lock refresh to be stuck behind the large uploads and thus time out.
5 lines
309 B
Text
5 lines
309 B
Text
Bugfix: Avoid lock refresh issues with slow network connections
|
|
|
|
On network connections with a low upload speed, restic could often fail backups and other operations with `Fatal: failed to refresh lock in time`. We've reworked the lock refresh to avoid this error.
|
|
|
|
https://github.com/restic/restic/pull/4304
|