290 minutes running for kjournald

jim.baker · 11-02-2009, 05:37 PM

i ran top on one of our servers, which has been giving us problems with having to restart the web server, and it showed the kjournald process with a running time of 290 minutes. This means it hasn't been restarted for a while, and neither has the server itself, but would this be causing the server to have problems, or is it normal to have it running this long. And, should it be restarted? how do u restart it?

thanks

esaym · 11-03-2009, 04:47 PM

What is the web server doing? Is it apache2?

unSpawn · 11-03-2009, 05:15 PM

Quote:

Originally Posted by jim.baker

the kjournald process with a running time of 290 minutes. This means it hasn't been restarted for a while, and neither has the server itself, but would this be causing the server to have problems, or is it normal to have it running this long.

(At least on 2.6.18) kjournald is a child of kthread. Both names show up in 'ps' in brackets meaning they're kernel processes. The kernel does handle VMM pretty well itself so you don't (need to) fiddle with it except through the appropriate sysctls.