Roch Bourbonnais wrote: >>> this came up sometime last year .. io:::start won't work since ZFS >>> doesn't call bdev_strategy() directly .. you'll want to use something >>> more like zfs_read:entry, zfs_write:entry and zfs_putpage or zfs_getpage >>> for mmap'd ZFS files >> > > Ed: > That's not entirely accurate. I believe ZFS does lead to bdev_strategy > being called and io:::start > will fire for ZFS I/Os. The problem is that a ZFS I/O can be servicing a > number of ZFS operations on a > number of different files (which is a great performance enabler). Given > that we can't map an I/O to a file, > iosnoop does not report the file info.
Still seems like iosnoop ought to be fixed, or a warning added. >> Ah ha! Maybe someone should report this to the right people and get the >> dtrace toolkit and dtrace demo programs fixed? > > Bill > Did the dtrace cmd I sent you gave any hints ? It gives far too much data. I haven't been able to correlate it with the disk activity. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
