On Thu, Feb 13, 2003 at 09:52:24AM +0200, Shachar Shemesh wrote: > I have never played with it myself (sorry, Muli), but I believe that > syscalltrack may do it.
No, syscalltrack can only be used currently to track "level 4", which would be Level 4: map process file accesses to file descriptors "PID 256 (/bin/foo) wrote 2048 bytes to file descriptor 7" Level 3 support will be added eventually (patches happily accepted ;-)). In regards to the original question, I don't know of any such capability for Linux that will not involve a moderate ammount of kernel hacking. > Eran Tromer wrote: > > >Greetings, > > > >How does one go about tracing *physical* disk I/O on Linux? > >Level 1: trace physical I/O requests: > > "wrote 4 sectors at offset 533624 on /dev/hda1" > >Level 2: report/filter-by PID: > > "PID 256 (/bin/foo) wrote 4 sectors at offset 533624 on /dev/hda1" > >Level 3: map physical locations back to files: > > "PID 256 (/bin/foo) wrote 2048 bytes to inode 535 (/tmp/foo)" > >To goal is to understand and reduce disk usage on a loaded system. > >It would suffice to get totals per file/process over several seconds > >instead of per-event notification. -- Muli Ben-Yehuda http://www.mulix.org http://syscalltrack.sf.net ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
