Hello! My gnome-tracker install appears to have broken itself slightly: tracker3 status reports “Database corrupt: database disk image is malformed” for hundreds of my music files. I can’t honestly tell if this is having any effect on anything I use Tracker for; I originally noticed this because Music was listing only a subset of my albums, so I started investigating, but it seems like maybe Tracker was just taking its time to reindex everything, for some reason? Music now appears to display something more like my full collection, at least.
I figure I can fix any lingering effects by tracker3 reset, but before I do that, is there anything useful I can do to help figure out what caused the corruption in the first place?
I noticed this error after removing folders from the Search Locations list in GNOME Settings. This is with Tracker 3.5.3.
For example, I switched off the Home folder from indexing, then found that file:///home/rodney was still listed in the results of tracker3 search but tracker3 status and tracker3 info file:///home/rodney would say “database disk image is malformed”.
Thanks for the info! I’ll try to reproduce the issue. Since you are still reproducing these database “corruptions” on >=3.5.x, it would be good to file a new issue to tracker, so we can request some more info there if needed.
FTR, this is just the fulltext-search index being corrupted, it is a correctable situation by rebuilding the FTS index, and that’s something that happens ootb with e.g. locale changes. I thought those were gone for good, but perhaps not…
Unfortunately I was unable to reproduce on 3.6/git, with or without TRACKER_DEBUG=fts-integrity. Since I am unclear if the issue was really fixed meanwhile, better let’s move this to a gitlab issue.
I haven’t yet learnt about the tracker SQLite schemas, and how the sparql store and FTS index fit together.
I was going to open an issue, but I have this problem with GNOME GitLab where my account keeps getting deleted! I created an account again, and will open an issue if I can reproduce this error after rebuilding the FTS index.