https://bugs.kde.org/show_bug.cgi?id=455179
--- Comment #4 from tagwer...@innerjoin.org --- (In reply to Valtti Rinnemaa from comment #3) > BTW: I was working on a personal project and did a git reset --hard and > changed the directory and file structure just before the bug started > occuring if my memory serves me right. Baloo should be able to cope if a file is deleted and another "appear" with the same inode. Normally it would be told of changes via iNotify but if it misses the notification, it would normally catch up after a relogon or "balooctl check". However it can get a bit stressed with "large scale" deletions. It can be that deletions "overflow" the iNotify queue - that is more than "sysctl fs.inotify.max_queued_events" happen. Also if there are a *load* of deletions these can take a while to process. I met this with Bug 437754. Your "git reset" might have been a bit hard on Baloo :-/ -- You are receiving this mail because: You are watching all bug changes.
