automake process is not necessarily the cause of the problem, it may instead be mostly a symptom.
99% IO is now being used by [kworker/u8:0+flush-179:0] which seemingly doesn't make any sense
IO column shows the percentage of the process's running time that is currently spent waiting on IO.1 So 99% for one (or some, or all) process(es) makes sense, it is just concerning.
[kworker/____] indicates a kernel thread. If anything is busy with IO, it is probably the kernel (it could by necessity mean the kernel in the context of
iotop, that would take some more investigation).
As already mentioned WRT this question,
automake is a component of Autotools, a suite of things used in configuring and executing a software build from source code (usually written in C and/or C++). If you've done something like this:
That's what started that. If
kworker are alternating in
iotop I would guess they are related to each other (ie., the
kworker is doing stuff for the userland process,
In any case, it may be a bit of cause for concern if you have processes constantly waiting on IO this way and your total disk access is ~32 K/s. It should be a lot faster than that.
This may be because the SD card is wearing out/has developed a defect. You should have a look at
dmesg output and int
/var/log/syslog to see if any IO errors are being issued.
- This implies a sampling period that is presumably quite short. If you want to dive deeper I'd start with that U&L link.