https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #6 from tagwer...@innerjoin.org ---
(In reply to Aaron Williams from comment #2)
> ... hence I use XFS.
It might still be worth the "sanity check" of running, for a file you know has
been indexed:
baloosearch -i filename:the-file-name
and see whether you get just the one hit. The number is the "docID", a
combination of the device and inode number. If you see several hits with
different docID's, you are on shifting sands. I'm afraid I don't know how XFS
behaves (and whether you have any extra layers) but it's worth keeping an eye
on the results from
stat the-file-name
and see if the device and inode numbers for the file change (for example over
reboots).
Igor Poboiko has a python "baloo-checkdb.py" script that checks the index for
consistency
https://invent.kde.org/frameworks/baloo/uploads/bdc9f5f17fc96490b7bd4a22ac664843/baloo-checkdb.py
See https://invent.kde.org/frameworks/baloo/-/merge_requests/87#note_535270 for
context
I would worry about trying it on such a large index, but who knows...
--
You are receiving this mail because:
You are watching all bug changes.
