High read rate on btrfs

Hi,
i’ve been using Garuda for quite some time as my main system and it’s been great so far. Recently i noticed quite high temps on my main NVME Drive which is a 1TB that has around 800 Gigs allocated to Garuda.

While digging around KSystem Monitor i noticed Garuda seems to be always reading from the disk at around 700-900 MB/s. This is my first BTRFS install, so admit i have no idea if this is just normal, but this still seems quite high and unusual - also, always having temps around 70-75°C on the NVME isn’t necessarily what i would call “beneficial” to the longevity of the drive. (And yes, i know, silicon aging isn’t much of an issue anymore…still…)

I’ve also checked Btrfs Assistant, there is no Scrub or Balance running, checking through KSystem Monitor as well, there is no process reading or writing that i can see.

Anyone got any suggestions where i could dig deeper? Are there any process monitors that specifically watch disk writes?

Thanks,
Nexusband

Please post your garuda-inxi as requested by the template.

Terminal:

htop

Then switch to I/O and take a look on DISK READ and DISK WRITE.

5 Likes

Thanks.

It was the baloo file indexer…no idea why it was stuck…turned it off and purged it.
https://wiki.archlinux.org/title/Baloo

1 Like

We always mark here the solution and not the implementation. :slight_smile:

1 Like

If the NVME reaches such temperatures just by reading, I would at least buy a passive heat sink for it.

Can’t, the GPU is in the way and the other 3 NVME Ports are also occupied. But, it takes about 2-3 hours to reach those temps, and 70-75°C is saturation temp…

however, after disabling baloo, the drive now runs a breezy 40°C…

Been reading various things about baloo, apparently it has a tendency to get stuck and re-read files…most people however talk about high ram and cpu usage.

Come to think of it and glancing at my taskbar, the CPU now runs at 33°C as well…checking homeassistant…well…power usage is down ~ 25 Watts (avg) as well.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.