https://bugs.kde.org/show_bug.cgi?id=438434
--- Comment #9 from tagwer...@innerjoin.org ---
So, you've purged the database and "baloo_index" counted 551,532 files to index
- then come back a bit later and it says 1,086,500 (and is ploughing slowly
through them)
The "device number" stat shows for the test file hasn't changed, so no
immediate explanation for where baloo found the "doubled" files.
If you search for the testfile - or maybe a file that "balooctl monitor" shows
as just having been indexed - and search for it
baloosearch --id ...fileindexedmorethanonce...
Do you get two/several results?
The --id option seems to be new and you can see the inode/device number in the
id. Thanks are due to skierpage for pointing it out in Bug 438527 :-)
You can give the "id" to balooshow -x and get the indexed details, including
the device number/inode of the file as indexed. So something like:
balooshow -x 1000be0000fc01
Maybe one small step further forward?
--
You are receiving this mail because:
You are watching all bug changes.
