I have a repo which when I
restic check it yields the following (besides some unreferenced packs):
pack 1e790c45: does not exist pack 867b890f: does not exist
In order to find what referenced them, I ran
restic find --pack 1e790c45 and
restic find --pack 867b890f, which to my surprise didn’t yield anything relevant at all - the following is the complete output:
enter password for repository: repository baa72e57 opened successfully, password is correct
Yep, nothing else. I believe I have previously used the
find --pack command successfully on other repositories, so I think it should indeed find something.
Any thoughts on this, is this expected to happen in some cases? If so, what case could possibly make
restic check tell me it’s missing a couple of packs, and then not be able to tell me what referenced those packs? Perhaps I’m missing something obvious here.
The end goal I’d like to reach is to forget and prune the snapshots that are affected by these packs missing, but I’m not sure how to do that now
restic 0.9.6 (v0.9.6-104-g58bd1652) compiled with go1.13.5 on linux/amd64