Missing chunks after running prune

Support
#21

Well that took too long, but after my 1 week prune it just failed with:
“2021-12-10 05:02:51.420 ERROR CHUNK_DELETE Failed to fossilize the chunk f481a22fd832c521169642bd1f21682edcfdd50e9c3ea5fea1455f7a97007865: Failed to retrieve the id of ‘chunks/f4/81a22fd832c521169642bd1f21682edcfdd50e9c3ea5fea1455f7a97007865’: googleapi: Error 400: Bad Request, failedPrecondition
Failed to fossilize the chunk f481a22fd832c521169642bd1f21682edcfdd50e9c3ea5fea1455f7a97007865: Failed to retrieve the id of ‘chunks/f4/81a22fd832c521169642bd1f21682edcfdd50e9c3ea5fea1455f7a97007865’: googleapi: Error 400: Bad Request, failedPrecondition”

Any ideas?

#22

I believe this failedPrecondition error is caused by exceeding the rate limit. It is unusual for the prune job to take more than a week. How large is your storage?

Now that the prune job has failed, you’ll need to run a check job with the -fossils option to make sure that there are no missing chunks/fossils. After than I would suggest running the prune with -exclusive without running any backup jobs at the same time. With -exclusive, unreferenced chunks/fossils are removed immediately, which should be much faster than the rename operation.