https://bugs.kde.org/show_bug.cgi?id=490981
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to Eugene Shalygin from comment #3)
> Although I use BTRFS, this behaviour can be observed without remounting the
> partition between indexing and queering.
If you want to step through the tests... Maybe there's an effect we've not
identified....
For one-of-your-files.txt, try:
$ baloosearch -i one-of-your-files.txt
You might get more then one "hit". The "-i" asks baloosearch to show the
internal DocID that Baloo uses, if you get more than one result with different
DocIDs and the same directory/filename then you'd had (now or sometime in the
past) the BTRFS device number problem.
You can check the details for the file on your filesystem with "stat":
$ stat one-of-your-files.txt
and make a note of the "Device" line. It will have the Device Number and iNode.
If you reboot the device number may change. Previously Baloo was confused by
this change, now it digs deeper and reads the FSID of the filesystem (which
does not change) and bases the DocId on that.
If you reboot and see the stat details change and baloosearch give the same
results as before, then you are on safe ground. You will however need to
reindex:
$ systemctl --user stop kde-baloo
$ baloctl purge
$ systemctl --user start kde-baloo
and you can watch the reindexing progress with "balooctl monitor". It might
take a while.
If your balooserch results continue to change, we'll have to dig down and see
what filesystem is (anything layered on top of BTRFS?)
--
You are receiving this mail because:
You are watching all bug changes.
