From aeed420e1aec8210e9a0f7c2774de18f53b3be79 Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Sun, 14 Nov 2021 17:52:41 +0100 Subject: [PATCH] add changelog --- changelog/unreleased/issue-2715 | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 changelog/unreleased/issue-2715 diff --git a/changelog/unreleased/issue-2715 b/changelog/unreleased/issue-2715 new file mode 100644 index 000000000..2401ce009 --- /dev/null +++ b/changelog/unreleased/issue-2715 @@ -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