mirror of
https://github.com/restic/restic.git
synced 2024-12-22 15:57:07 +00:00
add changelogs
This commit is contained in:
parent
4636c20397
commit
5af828e3e6
2 changed files with 28 additions and 0 deletions
14
changelog/unreleased/issue-3428
Normal file
14
changelog/unreleased/issue-3428
Normal file
|
@ -0,0 +1,14 @@
|
|||
Bugfix: List snapshots in backend at most once to resolve snapshot ids
|
||||
|
||||
Many commands support specifying a list of snapshot ids which are then used to
|
||||
determine the snapshot accessed by the command. To resolve snapshot ids or
|
||||
"latest" and check that these exist, restic listed all snapshots stored in the
|
||||
repository. Depending on the backend this can be a slow and/or expensive
|
||||
operation.
|
||||
|
||||
Restic now lists the snapshots only once and remembers the result to resolve
|
||||
all further snapshot ids.
|
||||
|
||||
https://github.com/restic/restic/issues/3428
|
||||
https://github.com/restic/restic/pull/3570
|
||||
https://github.com/restic/restic/pull/3395
|
14
changelog/unreleased/issue-3432
Normal file
14
changelog/unreleased/issue-3432
Normal file
|
@ -0,0 +1,14 @@
|
|||
Bugfix: Fix rare 'not found in repository' error for copy command
|
||||
|
||||
In rare cases copy (and other commands) could report that LoadTree(...)
|
||||
returned a `id [...] not found in repository` error. This could be caused by a
|
||||
backup or copy command running concurrently. The error is only temporary,
|
||||
running the failed restic command a second time as a workaround solves the
|
||||
error.
|
||||
|
||||
This issue has been fixed by correcting the order in which restic reads data
|
||||
from the repository. It is now guaranteed that restic only loads snapshots for
|
||||
which all necessary data is already available.
|
||||
|
||||
https://github.com/restic/restic/issues/3432
|
||||
https://github.com/restic/restic/pull/3570
|
Loading…
Reference in a new issue