https://bugs.kde.org/show_bug.cgi?id=438074
Frank Steinmetzger <dev-...@felsenfleischer.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dev-...@felsenfleischer.de
--- Comment #17 from Frank Steinmetzger <dev-...@felsenfleischer.de> ---
I’ve also been observing this problem for quite some time now. Thankfully, it
does not slow down my PC, even though it is 9½ years old. But I see it in the
system monitor applets in my panel that there is constant read I/O of 150 MB/s
for at least half an hour after login.
I ran balooshow -x on a file before and after the last two reboots and the
output was identical.
I don’t run btrfs. My system uses ext4 on LVM on LUKS. The output of lsblk also
remained unchanged across boots.
I’m not sure what else to check. I’ve issued balooctl suspend a few minutes
ago, but the indexer still chucks along. Eventually I killed the extractor with
killall.
```
~ LC_ALL=C time balooctl status
Baloo File Indexer is running
Indexer state: Suspended
Total files indexed: 176,898
Files waiting for content indexing: 74,305
Files failed to index: 0
Current size of index is 18.22 GiB
real 0m49,878s
user 0m0,013s
sys 0m0,004s
```
Addendum:
Reading this thread, I found out about `balooctl monitor` and started it, then
resumed the indexing. The monitor first printed some email files and there was
minor system load. Then a few seconds nothing and then the I/O load started
again, but the monitor has not shown any new filenames since.
Operating System: Arch Linux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
Kernel Version: 6.6.9-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz
Memory: 30.8 GiB of RAM
--
You are receiving this mail because:
You are watching all bug changes.
