https://bugs.kde.org/show_bug.cgi?id=437019
--- Comment #9 from David Kredba <nheghathivhis...@gmail.com> --- Yes, it is the same after log off/on. I am testing baloo for years but each time ending with balooctl disable balooctl purge and creating a new KDE profile to be sure that there is nothing left for a new indexing. It is getting better and better but never survived yet. I have 4 TB EXT4 FS created with -b 4096 and not optimized for big files, I think that that could be the source of the high inode count. Last indexing try I speeded up using a symlink of .local/share/baloo folder to a SSD drive. When done I moved it back. Can someone reproduce it please? Moving existing files indexed already to another folder and log off/on KDE session is sufficient for me. Thank you! -- You are receiving this mail because: You are watching all bug changes.
