https://bugs.kde.org/show_bug.cgi?id=446071
--- Comment #5 from tagwer...@innerjoin.org --- (In reply to sourcemaker from comment #4) > mdb_copy -n -c index index.new > ========================= > File Size: 26,50 GiB > Used: 2,50 GiB Hmm... Not as much space recovered as I hoped. I am guessing that won't help you much... There's a behaviour with LMDB that if one process is reading the index when another wants to write, the data written is appended. It's there to help "crash proof" the index. You might meet this in a baloo context if you do "balooctl status" as this counts the files "indexed" and "to be done". If you are counting a large number of files and indexing at the same time you might fall into the trap. I met it after deleting some thousands of files, have a look at Bug 437754 I wonder if your next step is to reindex from scratch, keeping an eye on progress with "balooctl monitor"; maybe restricting the directories you are interested in, at least initially. A common compromise is Documents, Music, Pictures, Videos -- You are receiving this mail because: You are watching all bug changes.
