Prune failing: chunk can't be found

Support
#1

Hi Gang,

I’m trying to prune a collection, and occasionally get the error like this:

Deleting snapshot xxx at revision 66
Deleting snapshot xxx at revision 67
Chunk 9c36c32b7ec6b68d3a6a44df77197a92d2f55ed95b3f7d460fad62351024d4c4 can't be found

It’s happened twice today. I’m not sure what’s going on? I’ve done some other pruning of a specific set of backups, but never using -exclusive. So it shouldn’t have lost any chunks, should it?

This has me concerned whether the backups are still viable, if it is missing chunks. What can I do?

Thanks Morgan

#2

okay, this is happening regularly. For each one of my snapshot ID’s, this has happened at least once. Here’s another example:

Deleting snapshot CentOS7Minimal@xxx at revision 79
Deleting snapshot CentOS7Minimal@xxx at revision 81
Chunk 46718d12f2150875089f53dbdd98520dc04a1e18aa61309268e2c1b832572760 can't be found

Maybe when it is looking for chunks, it is not looking for the ones already “fossilized” with .fsl? Or what else could be happening?