Remote missing files but list-broken-files returns 0

[mhas]

Thanks again @ts678!

@ts678

Although I think that’s fairly reliable, more certainty could be achieved by browsing DB

Excuse my ignorance, but what exactly would I be browsing for here?

@ts678

What type of Destination is this?

Backblaze B2. With my current lifecycle settings I think it may keep versions of files with the same name. I guess it’s best to keep only latest versions right? As suggested at Setting up retention/versioning with Backblaze B2? - #4 by mohak

So if I understand correctly, if I’m confident that the dindex files are citing useless dblocks (which I can confirm somehow by browsing the DB), I can just delete those four dindex files from B2, recreate DB, and cross my fingers right?

EDIT

@ts678

Do you know how much storage your backup takes?

Source:
33.81 GB
Backup:
56.28 GB / 45 Versions

Is this reasonable? Or should I check further whether there are dblocks that weren’t in any index?