https://bugs.kde.org/show_bug.cgi?id=520171
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] --- (In reply to martin-kokos from comment #0) > 1. Delete large directory with photos (a dataset, say 15000 images), I don't > know if this triggered baloo. I suspect it did. Yes, it will have triggered Baloo... Baloo gets a notification for each delete... > 2. Notice constant writing to disk (~60 MiB/s), confirmed its baloo via > iotop, check with fatrace its to baloo index ... and cleans the record in its index. It doesn't do that awfully well, it treats each delete separately so it gives itself a lot of work. In your situation, best to purge and reindex with a "balooctl6 purge". It won't take long to build a filename/metadata index. -- You are receiving this mail because: You are watching all bug changes.
