Re: loadavg always equal or above 1.00 - how to explain?

[Tomasz Chmielewski <mangoo@wpkg.org>]

Arjan van de Ven schrieb:
> On Thu, 2005-12-01 at 12:57 +0100, Tomasz Chmielewski wrote:
> 
>>1.00 1.10 1.06 1/65 782
>>
>>This server is barely used, and as I remember, loadavg was always
>>close 
>>to 0.00 on that system.
> 
> 
> remember that load is the sum of running/runable processes and processes
> in D state (waiting for IO generally, but not always). I'm pretty sure
> your load comes from one of the later...
> 
> ps ought to tell you which one it is... (if not, an 
> "echo t > /proc/sysrq-trigger" will dump the kernel state including the
> offending process, and will also tell us where exactly that process is)

Wohoo, you're great, that was it:

root     29547  0.0  0.3   7516   996 ?        D    Nov25   0:00 CROND
root     29548  0.0  0.3   7516   996 ?        Ss   Nov25   0:00 CROND

I stopped it, and loadavg is back to 0.

Now I have to figure out what CROND was doing...

Does ps always show processes in D state in CAPITAL letters?

After cron restart it is "crond", as usual.


-- 
Tomek
http://wpkg.org
WPKG - software deployment and upgrades with Samba