[F.A.Q.] filemon old-school en Bash

linux
1
  1. Make sure that syslog doesn’t log kern.debug to a file(check /etc/syslog.conf). if it does, disable it temporarily (better), or stop syslog altogether (worse, because you will eliminate one possible cause of the disk activity)
  2. type:

    echo 1 > /proc/sys/vm/block_dump
  3. in bash, type (modify to fit your favourite shell):

    while true; do dmesg -c; sleep 1; done;



    This effectively gives you a realtime live view of all disk activity

    note that if you didn’t dmesg -c since you booted, dmesg might contain a lot of info in the buffer, so let it barf everything onto the screen before attempting to actually read it.



    remember to restore things back to the way they were when you are done:
  4. echo 0 > /proc/sys/vm/block_dump
  5. restore syslog activity and/or kern.debug logging