https://bugs.kde.org/show_bug.cgi?id=457335
--- Comment #5 from tagwer...@innerjoin.org --- (In reply to Artur Rudenko from comment #4) > Why does it miss? It's a baloo bug or inotify problem? Maybe something of both... A historical "solved" case first; some distributions used to have a maximum number of folders that could be watched (fs.inotify.max_user_watches) rather low, see https://bugs.kde.org/show_bug.cgi?id=433204#c1. That caused issues in the past but is now generally OK. There is also however the size of the queue, fs.inotify.max_queued_events. If something creates more than this number of events, quicker than baloo can deal with them, then the queue will overflow. $ sysctl fs.inotify will show the values set in your system. In your example, if you unpack a zip containing *many* small files, you may hit the max_queued_events limit. Maybe perhaps you are creating a folder structure as part of the unpacking and baloo cannot set up the watches on the new folders before files are created within them. There are also the cases where baloo is busy (possibly when deleting a large bunch of files) and is not picking up the iNotify messages. > ... Maybe when iNotify notifies about a file created (or modified), baloo > should > mark parent folder as un-indexed? I think baloo could queue up a "balooctl check" if it gets a iNotify overflow failure. Possibly also if it suspects inconsistency but that feels messy. > ... But in real situation it is not. For example, try to unpack some archive > and > then search in unpacked folder. Baloo won't find anything and i think in > this case dolphin should just use a general search in this folder (while > adding it to index queue), but it doesn't, and it ends up in useless search > feature If you are extracting *many* files, then repeat with a larger max_queued_events. You might hit the limits when deleting loads of files (Bug 353874) and you could dig a hole for yourself if you repeatedly delete and create large numbers of files. Maybe check to see if you see the issue with "content indexing" disabled. If need full text indexing, be aware that baloo will deliberately "pace itself" when indexing the extracted files; it indexes a block of 40 files, then the next and the next and so on. I've occasionally wondered if a widget showing baloo's "rate of indexing" would give useful feedback -- You are receiving this mail because: You are watching all bug changes.
