TrueCloudLab/restic
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

add changelog

Browse source
This commit is contained in:
Michael Eischer 2021-11-14 17:52:41 +01:00
parent 9959190e39
commit aeed420e1a
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
changelog/unreleased/issue-2715 Normal file
View file

@ -0,0 +1,12 @@
Enhancement: Cancel commands if lock is not refresh in time
Restic commands kept running even if they failed to refresh their locks in
time. This can be a problem if a concurrent call to `unlock` and `prune`
removes data from the repository. Not refreshing a lock in time can for example
be caused by a client switching to standby while running a backup.
Lock handling is now much stricter. Commands requiring a lock are canceled if
the lock is not refreshed successfully in time.
https://github.com/restic/restic/issues/2715
https://github.com/restic/restic/pull/3569