dbbeac7174
The new option allows prune to operate with nearly no scratch space by only removing no longer necessary pack files and first deleting the index before rebuilding it. By first deleting the index it becomes safe to just delete no longer necessary pack files. However, as a downside there's now the risk that the repository becomes inaccessible if prune fails. To recover from that problem a user might have to manually delete the repository index and then run (a full) `rebuild-index` again.
9 lines
450 B
Text
9 lines
450 B
Text
Enhancement: Support pruning even after running out of disk space
|
|
|
|
When running out of disk space it was no longer possible to add or remove
|
|
data from a repository. To help with recovering from such a deadlock, the
|
|
prune command now supports an `--unsafe-recover-no-free-space` option to
|
|
recover from such situations. Make sure to read the documentation first!
|
|
|
|
https://github.com/restic/restic/issues/1153
|
|
https://github.com/restic/restic/pull/3481
|