Those of the OS X persuasion can find similar functionality in fs_usage.<p><a href="https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/fs_usage.1.html" rel="nofollow">https://developer.apple.com/library/mac/documentation/Darwin...</a>
I just added an experimental execsnoop to the repo as well: <a href="https://github.com/brendangregg/perf-tools" rel="nofollow">https://github.com/brendangregg/perf-tools</a> .
Great tool !
It is interesting because we are working to extract the same kind of information but with LTTng for low intrusiveness and remote analysis of production servers.
If you are interested, you can have a look at the following repository :
<a href="https://github.com/jdesfossez/lttng-analyses" rel="nofollow">https://github.com/jdesfossez/lttng-analyses</a>
If it's not reliable as claimed by the article, then does it really serve the purpose? There might be a code-path in an innocent little app that calls brk() often and then gets tainted as causing IO.<p>Aside, thanks for reminding me about blktrace. I had forgotten the name last week when I needed the tool.