Re: [PLUG] Which Process is Thrashing my Disk?

["Brian Vagnoni" <bvagnoni@v-system.net>]

atop? Requires kernel patch from what I've read.

You could use kill in a process of elimination guessing method. Kill process until the light stops blinky blinky.

I also found this script:

#!/bin/sh
case "$1" in --pids) SEL=2;; --procs) SEL=1;;
--files|*) SEL=9;; # how come I can't use NF?
esac; for tree in home proc dev usr var; do 
echo -n "/$tree: "; lsof -w -n -a -d0-10 -a +D \
/$tree|grep '[0-9][urw]'|awk --assign VAR="$SEL" \
'{print $VAR}'|sort|uniq|xargs; done; exit 0

You could look at which processes are using the most virtual memory assuming you have a swap, right?

Pulling out the books so I may have more info for you.


--------------------------------------------------
Brian Vagnoni
PGP Digital Fingerprint
F076 6EEE 06E5 BEEF EBBD  BD36 F29E 850D FC32 3955
--------------------------------------------------


----- Original Message -----
From: brent timothy saner
[mailto:brent.saner@gmail.com]
To: Philadelphia Linux User's Group
Discussion List [mailto:plug@lists.phillylinux.org]
Sent: Sat, 14 Jun
2008 14:38:41 -0400
Subject: Re: [PLUG] Which Process is Thrashing my
Disk?


> Brian Vagnoni wrote:
> > I should give you a search google chiding.
> > 
> > But here you go 
> > 
> > 
> >
> http://www.nslu2-linux.org/wiki/HowTo/IdentifyWhichProcessesAccessDisk
> > 
> > or
> > 
> >
> http://www.linux-tutorial.info/modules.php?name=Forums&file=viewtopic&t=795
> 
> 
> 
> not helpful.
> 
> "In many cases this won't tell you anything especially if you are
> using
> a journalling filesystem."[1]
> i.e. ext3, reiserfs (i believe), jfs (also as i recall)... and, by
> extension, ntfs-3g mounts.
> 
> the second one..well, that just covers lsof, not the actual I/O.
> 
> 
> 
> 
> casey, i must preface this first that /there is no real way to
> accurately determine I/O/, simply because of the channel architecture.
> and you may have varying levels of success based upon what kind of
> disk
> it is. however, if you want a pretty good idea, i'd do:
> 
> watch -no.5 -d iostat
> 
> 
> this puts a watch on iostat's output which updates every half-second
> and
> hilights differences.
> 
> you might want to poke through iostat's man page, as there's a LOT of
> interesting info in there (i think there may be an iostat builtin that
> does what i specified above).
> 
> 
> 
> [1]http://www.nslu2-linux.org/wiki/HowTo/IdentifyWhichProcessesAccessDisk
> bottom of page
> 
> -- 
> brent saner.
> gpg info at http://www.notebookarmy.org/gpg.txt
> (this is a shorter sig.)
> 
> grep -i hotchicks *
> 
> 
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug