Hi Neel - Thanks for pushing this out. I've been tripping over this for
a while.
You can instrument zfs_read() and zfs_write() to reliably track filenames:
#!/usr/sbin/dtrace -s
#pragma D option quiet
zfs_read:entry,
zfs_write:entry
{
printf("%s of %s\n",probefunc, stringof(args[0]->v_path));
}
I'm not sure why the io:::start does not work for ZFS. I didn't spend
any real time on this,
but it appears none of the ZFS code calls bdev_strategy() directly, and
instrumenting bdev_strategy:enter (which is where io:::start lives) to track
filenames via stringof(args[0]->b_vp->v_path) does not work either.
Use the zfs r/w function entry points for now.
What sayeth the ZFS team regarding the use of a stable DTrace provider
with their file system?
Thanks,
/jim
Neelakanth Nadgir wrote:
> io:::start probe does not seem to get zfs filenames in
> args[2]->fi_pathname. Any ideas how to get this info?
> -neel
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
