I asked if Compact got run manually, and now I’ll ask about Test which looks
like it runs VerifyConsistency which is what makes the complaint being seen.
I know Compact has been a source of pains, but the exact sequence is hard
to see from the bug report because logs were deleted to protect user privacy.
I’m guessing Duplicati won’t be able to name which files were broken, as the
highest level problem is FilesetEntry referencing nonexistent File table rows.
SELECT * FROM “FilesetEntry” LEFT JOIN “FixedFile” ON “FilesetEntry”.“FileID” = “FixedFile”.“ID” WHERE “FilesetEntry”.“FilesetID” = 205 AND “FixedFile”.“ID” IS NULL
205 is special because SQL wouldn’t complete, unlike with prior ID values.
Turns out that query planner (that again) chose to scan rather than search:
Problem was fixed by adding an index to FixedFile (originally the File view):
One symptom of a scan is in an enormous number of database reads shown
by tools such as Sysinternals Process Monitor or I/O Reads in Task Manager.
This might not actually show up at the drive level because the OS soaks it up.