forked from TrueCloudLab/restic
doc: prune --max-unused unlimited will still repack metadata
Adding minor clarification to documentation of `prune --max-unused unlimited` to indicate metadata will still be repacked. The referenced PR indicates `max-repack-size` CAN limit metadata repacking. Ref: https://forum.restic.net/t/max-unused-unlimited-still-repacks/3661 Ref: https://github.com/restic/restic/pull/3228
This commit is contained in:
parent
88a23521dd
commit
aa0a7b78a8
1 changed files with 1 additions and 1 deletions
|
@ -341,7 +341,7 @@ The ``prune`` command accepts the following options:
|
|||
unused files. This means that as long as some data is still used within
|
||||
a file stored in the repo, restic will just leave it there. Use this if
|
||||
you want to minimize the time and bandwidth used by the ``prune``
|
||||
operation.
|
||||
operation. Note that metadata will still be repacked.
|
||||
|
||||
Restic tries to repack as little data as possible while still ensuring this
|
||||
limit for unused data.
|
||||
|
|
Loading…
Reference in a new issue