Output of restic version
restic 0.17.1 compiled with go1.23.1 on linux/amd64
What backend/service did you use to store the repository?
rclone using pcloud (EU server) as backend
Problem description / Steps to reproduce
When error occurs:
running a regular prune job with following command:
restic forget
–keep-daily 7
–keep-weekly 4
–keep-monthly 12
–prune
–max-unused 0
-r $TARGET \
Output:
Applying Policy: keep 7 daily, 4 weekly, 12 monthly snapshots
keep 10 snapshots:
…
…
1 snapshots have been removed, running prune
loading indexes…
loading all snapshots…
finding data that is still in use for 10 snapshots
[0:07] 100.00% 10 / 10 snapshots
searching used packs…
{<data/a16a2f18> <data/c6645551> <data/bf414c8d> <data/a909b67f> <data/67e700b1> <data/aca3d8c2> <data/f647935c> <data/51a01e28> <data/ef5dd98c> <data/91e6871e> (4 more)} not found in the index
Integrity check failed: Data seems to be missing.
Will not start prune to prevent (additional) data loss!
Please report this error (along with the output of the ‘prune’ run) at
Sign in to GitHub · GitHub
Fatal: index is not complete
Expected behavior
I understand the repo is damaged but I am looking for an easy way to get the repo healthy again.
Actual behavior
Currently, no way to run prune as will always have this fatal error and won’t remove older snapshots.
Do you have any idea what may have caused this?
pcloud EU server does seem to hvae issues. I also do another backup job on pcloud US server and it is totally fine.
I just wish there was better recovery tools to fix in case of errors like this as I dont want to reupload the whole 800Gb repo.
Did restic help you today? Did it make you happy in any way?
Restic is great and I really hope can help further contribute to development!