New answers tagged io
Use iotop. It should be available in your repo for a Redhat/Centos/Fedora machine (if it is not already installed). It outputs a similar info as top, but instead of the CPU/memory stats, you will get the IO stats (Disk reads, writes and swapin). The options -p , -u and --only might be of interest to you. For example, to see the IO activity of the ...
You can use iotop -b (batch mode) inside of a loop based on # of seconds. That will spit out everything and then redirect it to a file. I'm trying to find a shell loop example to do that but i don't do shell programming much. If i started the command by hand, i would run: iotop -botqk > ~/log-iotop.txt or something similar. Hope that helps!
http://en.wikipedia.org/wiki/Asynchronous_I/O, a program is firing up requests for I/O, but does not wait on them. However it can still accept and process the I/O responses once they come.
There looks to be a single thread writing a little bit more than 4KB about 111 times per second. This is sufficient to keep your disk 100% busy (111 iops * 9 ms service time = 1 second of service per second = 100%). As there are no other processes writing on that disk (that partition actually), the wait queue is empty, all requests are processed immediately. ...
The only thing that comes close is iostat from the sysstat suite which also works for regular users or maybe atop -d (fails with a floating pointing exception here). Nearly same question was already asked here: http://serverfault.com/questions/260818/in-absense-of-iotop-which-command-is-most-appropriate-for-get-i-o-bounded-proces iotop doesn't work for ...
Top 50 recent answers are included