https://bugs.kde.org/show_bug.cgi?id=437019
--- Comment #2 from David Kredba <nheghathivhis...@gmail.com> --- Total files count is constant, I tested moves of existing files. Found it when I needed to ran rsync over ssh in the morning being short on time and saw its slowness so went to check what is slowing the disks down. Found indexing of content of files where there was zero to be indexed the day before session log-off (shut down of the machine). What grows from zero during log-off/log-on is the count of the files waiting to be indexed }if there was file move - and rename too). And it is exactly the count of moved files, it can be seen because I am using it on top of EXT4 fs on top of LUKS on top of a MD Raid 1 on a pair of rotating hard disks. Yes, I can see it during "monitor" session. I set fs.inotify.max_user_watches = 2048000 long time before I started using Baloo. find . -type f | wc -l returns 503013, so there is a reserve for inotify. When I tried "balooctl check" after files moved it not started to index and the count of files waiting for indexing stayed at 0. Each time I tested it. I will test the stat case. Is noatime fine for baloo please? (maybe it can be that simple) LABEL=HOME /home ext4 noatime Thank you. -- You are receiving this mail because: You are watching all bug changes.
