[frameworks-baloo] [Bug 520171] Excessive index size, only basic indexing
https://bugs.kde.org/show_bug.cgi?id=520171 [email protected] changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from [email protected] --- (In reply to martin-kokos from comment #3) > I forgot to mention, I've seen the file grow from 6GB *after* the deletion > which seemed odd, which prompted me to submit a bug. Thank you for doing the work of writing it up... Baloo gets notified of the deletes, queues the info and then starts removing the records. If you do the same again and watch with htop, you'll see baloo_file working hard to "catch up" for a while after you've removed the files. I'll flag as a duplicate of 442453, it seems to be close enough *** This bug has been marked as a duplicate of bug 442453 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 520171] Excessive index size, only basic indexing
https://bugs.kde.org/show_bug.cgi?id=520171 --- Comment #3 from [email protected] --- I forgot to mention, I've seen the file grow from 6GB *after* the deletion which seemed odd, which prompted me to submit a bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 520171] Excessive index size, only basic indexing
https://bugs.kde.org/show_bug.cgi?id=520171 --- Comment #2 from [email protected] --- Thanks a lot for the suggestion. I've made a copy of the index file in case its useful to inspect it. If its a known issue, feel free to close. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 520171] Excessive index size, only basic indexing
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.
