Re: tracking down i/o sucking process

Am 2003-11-03 12:40:58, schrieb Dan MacNeil: the command: top ..is great for CPU RAM but doesn't do disc... fuser -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?

Re: tracking down i/o sucking process

Am 2003-11-03 12:40:58, schrieb Dan MacNeil: the command: top ..is great for CPU RAM but doesn't do disc... fuser -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org.

tracking down i/o sucking process

I'm sure this info is googlable but after 30 minutes I can't find it... I can hear the discs on the server going wild, I run: sar -d 2 120 ...and disc utilization is indeed higher than normal. How do I find what process is driving up the i/o load? the command: top ..is great for CPU

Re: tracking down i/o sucking process

Dan MacNeil wrote: I can hear the discs on the server going wild, I run: sar -d 2 120 ...and disc utilization is indeed higher than normal. How do I find what process is driving up the i/o load? Not sure about I/O load specifically... but try lsof and see what processes have which files

tracking down i/o sucking process

I'm sure this info is googlable but after 30 minutes I can't find it... I can hear the discs on the server going wild, I run: sar -d 2 120 ...and disc utilization is indeed higher than normal. How do I find what process is driving up the i/o load? the command: top ..is great for CPU

Re: tracking down i/o sucking process

Dan MacNeil wrote: I can hear the discs on the server going wild, I run: sar -d 2 120 ...and disc utilization is indeed higher than normal. How do I find what process is driving up the i/o load? Not sure about I/O load specifically... but try lsof and see what processes have which files