https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #18 from Igor Poboiko <igor.pobo...@gmail.com> --- We would really appreciate if someone who experiences this could send us a corrupted "~/.local/share/baloo/index" entry. Just be aware that it will most likely contain a lot of personal information. If you don't want it to be exposed, make sure to add folders which you don't want to be indexed to "Do not search in these locations", inside "SystemSettings -> Search -> File Search". Alternatively, you can create a new user (with no personal information at all), and try to reproduce it. Thanks! > Even after I clear all folders, the file size won't change. > The command 'balooctl indexSize' shows that the used space is much smaller. > But it seems that it remains something broken within the index file. It's one of the peculiarities of the underlying database, LMDB. It uses Copy-on-Write, and database actually doesn't shrink. But it can reuse memory pages that became free later on (so after clear&reindex, db size might actually not change at all). > Another curious thing. I'm indexing only the file names, and not the content. > Nonetheless, the process feels a bit too fast. Disabling and re-enabling > baloo, the re-indexing process is almost instantaneous. > Is it actually running the file name indexing from scratch? > Or using some backup of the index file stored in a cache somewhere? Filename indexing should be quite fast (don't know how fast is "too fast" though - but I think it takes less than a second in my case, which is ~13.5k documents inside index). Baloo don't have any backups / caches for it, it only can redo it from scratch. -- You are receiving this mail because: You are watching all bug changes.
