@Kyle, thanks for looking into this. The clients are VMWare esx 4.0u1 machines so unmounting their datastores is a bit difficult since they are production machines.
I fail to see the relation between the nfs client and the iopattern dtrace script for example. That script is supposed to opperate on the local filesystem right? So why doesn't it register any i/o's for a file being actively modified? All I want to monitor is the amount and size (as second step) of the i/o's per virtual disk. Any suggestion is more than welcome. Frederik On Mon, Feb 28, 2011 at 7:03 PM, Kyle Hailey <kyle.hai...@delphix.com> wrote: > > The file names are cached and if there is some problem on the client then the > cache might be missing the names. The cache is populated by VOP_LOOKUP() but > if vnode_t v_path is NULL then VOP_LOOKUP() was never run which can only > happen when there is some issue on the client like possibly a reboot and the > vnode is obtained from VFS_VGET(). > Try umount/mount of the filesystem on the client and see if it refreshes the > cache. > - Kyle Hailey > http://dboptimizer.com > > On Mon, Feb 28, 2011 at 1:26 AM, wessels <wessels...@gmail.com> wrote: >> >> Hi, >> >> sorry to post this again but my first post didn't make it to the mailing >> list. >> >> I'm trying to monitor a file, via the iopattern script from the DTrace >> toolkit, which resides on a ZFS filesystem and is being modified by a >> remote NFS client. I tried this on b104 and b125 nothing more recent. >> Plain iopattern without options shows i/o counters as output but when >> I supply the filename via the -f parameter all fields remain zero. >> I also tried the following oneliners below: >> # ./nfsv3fileio.d >> Tracing... Hit Ctrl-C to end. >> ^C >> >> Rbytes Wbytes Pathname >> 41631744 41421266 <unknown> >> >> # dtrace -n 'nfsv3:::op-read-start,nfsv3:::op-write-start { >> @[probefunc,args[1]->noi_curpath] =count(); }' >> dtrace: description 'nfsv3:::op-read-start,nfsv3:::op-write-start ' >> matched 2 probes >> ^C >> >> rfs3_read <unknown> 867 >> rfs3_write <unknown> 3470 >> # dtrace -n 'fsinfo:::read,fsinfo:::write { >> @[probefunc,args[0]->fi_pathname] =count(); }' dtrace: description >> 'fsinfo:::read,fsinfo:::write ' matched 2 probes >> ^C >> >> fop_read /etc/default/nfs 2 >> fop_read /etc/resolv.conf 6 >> fop_read <unknown> 155 >> fop_write <unknown> 619 >> >> Any ideas why this happens, that's the <unknown>? Yes, the i/o are >> detected but on which file? >> >> Thanks, >> >> Frederik >> _______________________________________________ >> dtrace-discuss mailing list >> dtrace-discuss@opensolaris.org > > > > -- > - Kyle > O: +1.415.341.3430 > F: +1.650.494.1676 > 275 Middlefield Road, Suite 50 > Menlo Park, CA 94025 > http://www.delphix.com > _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
