Hi @budy, thanks for the answer. I see, I suspected something like that by the amount of small files affected by just a handful of blobs.
After my tests I too I’m of the thinking that kopia can’t currently fix those blobs with the available cli. I was hoping that it worked somehow like in restic where rebuild-index + snapshot does indeed fix missing blobs. I guess there’s always tradeoffs.
I do wonder if it is possible to implement this kind of recovery in kopia though, since deduplication must rely on the same blobs being obtained for the same input files, even if new files appear in the mix. So I guess some kind of e.g. snapshot fix replay should be doable to fix any missing/damaged blobs, as long as the original sources are available, of course.
Since losing a blob to bitrot or backend malfunction doesn’t seem that far-fetched (yes, I know our backends should be trustable), it would be a nice feature to have for extra peace of mind, specially since it can save a lot of snapshot history. Maybe it’s simple enough to implement that the effort/benefit ratio allow it.
Have you tried to only mount the latest snapshot?
I can mount all of them, no problem, and all of them have the same broken files, as expected.
In the end I’ve gone the route of fix invalid-files + new complete snapshot. I know how to reproduce the issue easily though and have compiled kopia from sources in the past, so I’d be willing to help implement/test this feature.