Kenn Humborg writes:
> > > Kenn Humborg wrote:
> > > > Running vmstat 1 on a machine shows me a certain amount of block I/O.
> > > >
> > > > But, short of strace-ing everything running on the machine, how can
> > > > I determine which processes are generating this I/O?
> > > >
> > > > lsof will show me open files, but that doesn't help much.
> > >
> > > echo 1 > /proc/sys/vm/block_dump
> > > tail -f /var/log/debug
> > OK - that's a good starting point. I suppose a better approach
> > might be to fire the kern.debug messages to syslog on another
> > machine so that syslog I/O doesn't cause a feedback loop
> > (process writes to block, kernel writes debug message, syslog
> > writes to /var/log/debug, kernel writes debug message, etc...).
>> Not really as useful as I expected, unfortunately. It's easy enough
> to see who is reading blocks, but all the writes are attributed to
> kjournald or pdflush.
What about if the fs is mounted with the 'sync' flag?
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!