https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #2 from Martin Steigerwald <mar...@lichtvoll.de> --- I disabled it completely for now, cause an index size of 17 GiB, is more that I am willing to accept: LANG=C balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 542390 / 559358 files Current size of index is 17.64 GiB That index size raised during about indexing maybe 3000 new files. It was basically crunching around 540000 files for *hours*. During that time it added about 8 GiB for the index. According to balooctl indexSize there is clearly a bug somewhere: balooctl indexSize Actual Size: 17,64 GiB Expected Size: 6,31 GiB PostingDB: 1,70 GiB 73.408 % PositionDB: 2,49 GiB 107.739 % DocTerms: 1,15 GiB 49.863 % DocFilenameTerms: 56,76 MiB 2.397 % DocXattrTerms: 0 B 0.000 % IdTree: 10,19 MiB 0.430 % IdFileName: 42,19 MiB 1.781 % DocTime: 25,41 MiB 1.073 % DocData: 34,28 MiB 1.448 % ContentIndexingDB: 540,00 KiB 0.022 % FailedIdsDB: 4,00 KiB 0.000 % MTimeDB: 11,02 MiB 0.465 % Just see actual versus expected size. I am willing to keep this index for a while in case you'd like me to run some command on it. I now see something else in ~/.xsession-errors: "somefilename in home" id seems to have changed. Perhaps baloo was not running, and this file was deleted + recreated This message appeared more than 150000 times in ~/.xsession-errors: % grep -c "Perhaps baloo was not running" ~/.xsession-errors 153331 The files are on an BTRFS RAID 1 and most have not been changed… however I stopped Baloo due to excessive resource usage quite often already. Thus, yes, it has not been running all the time. -- You are receiving this mail because: You are watching all bug changes.