mirror of
https://github.com/restic/restic.git
synced 2025-08-23 22:37:25 +00:00
prune: correctly account for duplicates in max-unused check
The size comparison for `--max-unused` only accounted for unused but not for duplicate data. For repositories with a large amount of duplicates this can result in a situation where no data gets pruned even though the amount of unused data is much higher than specified.
This commit is contained in:
10
changelog/unreleased/pull-5212
Normal file
10
changelog/unreleased/pull-5212
Normal file
@@ -0,0 +1,10 @@
|
||||
Bugfix: Correctly account for duplicate data in `prune --max-unused`
|
||||
|
||||
`prune --max-unused size` did not correctly account for duplicate data.
|
||||
If a repository contained a large amount of duplicate data, this could
|
||||
previously result in pruning too little data.
|
||||
|
||||
This issue is now resolved.
|
||||
|
||||
https://github.com/restic/restic/pull/5212
|
||||
https://forum.restic.net/t/restic-not-obeying-max-unused-parameter-on-prune/8879
|
Reference in New Issue
Block a user