Jim,
thanks a lot for your suggestions! I just came up with a different solution a
few minutes ago, here it is:
as the filesystem IO read and writes are always embedded in opens and closes,
and I know the name of the UNIX domain socket, I can match against that in
open:entry:
syscall::open*:e
You could first filter out the target file system for the file IO by
doing a count() aggregation on;
[fds[arg0].fi_fs] = count();
NOTE - this will only work for those system calls that take a file
descriptor as arg0.
Once you know the FS target for the file IO (ufs? zfs? whatever), use it
in a
Dtracers,
I'm investigating some performance issues using a simple dtrace script which
collects read,write,stat,... syscall data. This works fine and gives me some
good data.
Unfortunately the app I'm tracing is concurrently doing file IO and IO on a
UNIX domain socket. As I'm only interested i
