On Tue, 2008-05-20 at 09:06 -0400, David Fix wrote:
quoted text
> Hey Dave,
> 
> Thanks for following up on this...  The previous kernel that I was 
> running was 2.6.18.1...  From CentOS 5.1.
> 
> It appears that the thread eating up that much CPU isn't a continuous 
> happening, only when there's a fair amount of activity going on.  It's 
> hard to nail down exactly when it happens, but the next time it does, 
> I'll definitely let you all know!

Since it's only happening during periods of high activity, it doesn't
seem as serious a problem as I suspected it may be.  Several threads
operating on a lot of files and/or directories at one time could put a
lot on the jfsCommit thread's queue, even though 99% cpu utilization
still seems high.

quoted text
> I haven't been able to reboot this machine, as it's a production unit, 
> but if I do get the chance, I'll do so.

Since the thread isn't stuck in some kind of infinite loop, I don't
really think a reboot will make any difference.  When I asked I wasn't
sure if the thread was continuously munching cpu.

quoted text
> It seems to have leveled out 
> now, with there being no high usage at all on there right now.

If you see it again, Christian's suggesting of running oprofile to see
where the the cpu is spending most of its time might be helpful.

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/