Release: 2.1.0.120 (Canary) 2025-06-24

[jberry02]

Problem as reported in the .119 thread:

@jberry02

I have one backup that keeps giving this error:

Detected 176676 file(s) in FilesetEntry without corresponding FileLookup entry

Database repair doesn’t seem to help - anything else to try?

@jberry02

Resorted to a database “delete and recreate”. Even after that I had to do a repair, and I think I also had to do a “purge-broken-files”. But I have the backup working again.

@jberry02

And it is back again…

Detected 332807 file(s) in FilesetEntry without corresponding FileLookup entry

@jberry02

First, upgraded to .120, then trying to do a database “Delete and Recreate”, but it keeps failing with “The requested file does not exist”. On the latest attempt it failed during “Pass 3 of 3, processing blocklist volume 614 of 616”, so right at the end. I believe the prior attempts also failed near the end but I neglected to check for the details.

@jberry02

Trying to do a database “Delete and Recreate”, but it keeps failing with “The requested file does not exist”. On the latest attempt it failed during “Pass 3 of 3, processing blocklist volume 614 of 616”, so right at the end. I believe the prior attempts also failed near the end but I neglected to check for the details.

Analysis: Since it can’t recreate the database, the issue is with the files in the b2 bucket. As backups were running without any apparent error prior to this, it seems that the issue is:

1. an error in the last backup’s fileset
2. a more severe error with the rest of the files

If the problem was case 2, there really isn’t anything I could do without special guidance.

Assuming case 1, the obvious action is to delete the most recent backup. However, that fails presumably due to the underlying error.

So instead I pursued a more drastic action. First, using rclone I created a copy of the directory containing the backup files (safety first!), and then deleted the most recent dlist file. After this I was able to do a database “Delete and Recreate” that ran to completion, and I am happy to report that so far it has completed 3 nightly backups without any apparent errors (it did report fixing an index file, but I am getting those on other backups as well).

Hopefully this is now permanently resolved.