TheArchive/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2025-07-30 21:03:37 +00:00
Code Issues Packages Projects Releases Wiki Activity
restic/changelog/0.18.0_2025-03-27/pull-5212

9 lines
412 B
Plaintext
Raw Normal View History

Polish changelogs (#5308) * polish changelogs * Additional changelog polishing * fix test failure * Correct changelog for recover command --------- Co-authored-by: Leo R. Lundgren <leo@finalresort.org>
2025-03-25 18:12:51 +01:00
Bugfix: Fix duplicate data handling in `prune --max-unused`
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.
2025-01-18 22:15:35 +01:00
Polish changelogs (#5308) * polish changelogs * Additional changelog polishing * fix test failure * Correct changelog for recover command --------- Co-authored-by: Leo R. Lundgren <leo@finalresort.org>
2025-03-25 18:12:51 +01:00
The `prune --max-unused size` command 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 has now been fixed.
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.
2025-01-18 22:15:35 +01:00
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 Copy Permalink