I think I have an extreme case of prune on restic 0.9.2.
Here is what I’m getting after a few forgets…
restic -r s3:https://firstname.lastname@example.org/myrepo prune --cleanup-cache repository xxxxxxxx opened successfully, password is correct counting files in repo building new index for repo [2:42:50] 100.00% 181230 / 181230 packs repository contains 181230 packs (4316033 blobs) with 791.943 GiB processed 4316033 blobs: 70413 duplicate blobs, 15.426 GiB duplicate load all snapshots find data that is still in use for 3155 snapshots [28:52] 100.00% 3155 / 3155 snapshots found 4100014 of 4316033 data blobs still in use, removing 216019 blobs will remove 0 invalid files will delete 8524 packs and rewrite 14864 packs, this frees 58.097 GiB [29:48:33] 17.81% 2648 / 14864 packs rewritten
and still running…
If I ask what is in the cache I get
$ du -d 1 -h ~/Library/Caches/restic/xxxxx/ 7,0G /Users/vartkat/Library/Caches/restic/xxxxx//data 513M /Users/vartkat/Library/Caches/restic/xxxxx//index 12M /Users/vartkat/Library/Caches/restic/xxxxx//snapshots 7,5G /Users/vartkat/Library/Caches/restic/xxxxx/
Did I do something wrong or is it normal to get such delays ?
According to these numbers there is still
137 hours, means 5 days and 17 hours to go.
What is restic doing ? Is it downloading everything and re-uploading it ?
Why such a delay, can you detail the operation ?