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.
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? Contact [EMAIL PROTECTED]
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 open. You'll probably want to grep -v a lot of stuff- I get 664 lines on a pretty barebones NAT firewall box. :/ HTH, -kgd -- hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is.
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 open. You'll probably want to grep -v a lot of stuff- I get 664 lines on a pretty barebones NAT firewall box. :/ HTH, -kgd -- hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
