https://bugs.kde.org/show_bug.cgi?id=500665
--- Comment #46 from tagwer...@innerjoin.org --- That's a lot of information to sort through... I'm not going to be able get to the bottom of each of the points. There a handful of good things, a few questions and some bits of advice though. You are running with the ntfs3 driver now (not the ntfs-3g) and the system's working better. That is good. Your "balooctl status" says you have 4,366,8011 files, could that be true? You have an index size of 57.33 or 61.38 GB, which is wildly large. Your "balooctl indexSize" says 2.92 GB actually used. That should not be... I see on my system, if I start Baloo with a "balooctl enable" (maybe you have to give the command twice, it might not immediately start), then you are just running the binary. If you start it with "systemctl start --user kde-baloo", you are running it "within" the limits on memory; it cannot use more than 512 MB of RAM. You can check with "systemctl status --user kde-baloo" whether Baloo is running within the systemd limits. On my system it looks as if, if you do a "balooctl enable" and then try a "systemctl start --user kde-baloo", you get that "not able to start" failure that you saw.... As a heads up... If you have such a large index you will notice performance problems if you run "balooctl enable". The systemd limits prevent that although maybe the 512MB is too small. We might come back to that later. I think you have to take a step back, swallow, purge the index and start again. You've got the ntfs3 kernel (rather than FUSE) drivers so you should be faster. Make sure you are running under the systemd memory limits. These should stop Baloo taking too much RAM and affecting performance. Keep a look out for multiple hits for a file, the "baloosearch -i one-of-your-files.txt", that will be a clear warning that something is wrong. Check whether you really have over 4 million files you want to index, maybe you have 2 million and they are counted twice (that would be another pointer to something wrong). It's also probably wrong to run and repeatedly rerun "balooctl status" in order to watch how the number of indexed files is changing, there's a bug about how this makes the index size grow (horribly grow). I'll see if I can find it... I'm wondering about the iNotify limit warning, that's something that used to cause trouble but has not recently. We can come back to that later as well. Final snippet of info, if you are getting "balooctl monitor" showing lines with a plain "OK" and no filename, don't worry. Baloo has looked at the file and it is excluded on account of its Mime type. Yes, this diagnostic could be improved... -- You are receiving this mail because: You are watching all bug changes.
