similar to: NFSv3 provider

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i''m trying to use the nfsv3 provider on S10U6, with the following simple script: #! /usr/sbin/dtrace -s #pragma D option quiet nfsv3:::op-read-start { printf("%s\n", args[1]->noi_curpath); } however, when running it, i get the following error: dtrace: failed to compile script ./nfs2.d: line 5: failed to grab

We recently had a strange NFS performance anomaly between a V880 running snv_124 and two NetApp filers. To investigate, a DTrace NFSv4 (and eventually NFSv3) client provider would been extremely helpful. Unfortunately, all I could find were a request for code review of a v3 client provider and another request for help developing a v4 provider. Nothing seems to have come from those initiatives,

Hi, Thanks for the comment for my nfsv3client probe implementation! I have made changes accordingly. Webrev: http://cr.opensolaris.org/~danhua/webrev/ To reduce the overhead, I use a local variable to save XID, rather than alloc memory space with kmem_zalloc(). According to the overhead caused by tsd_get() and tsd_set(), I did an experiment to measure it. In this experiment, I run a dtrace

Howdy, I wrote a pair of scripts to measure file and NFSv3 operations, and thought I would share them with the folks on the list. You can view the script output by pointing your browser at the following URLs: Per Process NFSv3 Client statistics (inspired by fsstat/nfsstat): http://daemons.net/~matty/code/nfsclientstats.pl.txt Per Process File Operations (inspired by fsstat):

Hi, This is a proposal for probes for NFS v3 client(see attachment). These probes are under a new DTrace provider: nfsv3client. These new probes support tracing NFS v3 client activities such as sending RPC requests to NFS v3 server and receiving RPC replies from NFS v3 server. Formats and arguments of these new probes are quite similar to existing NFS v3 probes on server side (provider: nfsv3).

I want to list/use the nfs probes but I get the error "dtrace: failed to match nfs*:::: No probe matches description". Is there a way to enable nfs provider probes? My system is running snv_112 (bfu''ed from the gate archive) # dtrace -lP nfs* ID PROVIDER MODULE FUNCTION NAME dtrace: failed to match nfs*:::: No probe matches

DTrace folks, I''m pleased to introduce a potential new DTrace-sponsored project: the Erlang DTrace provider. To be good OpenSolaris citizens, we want to put the formation of this officially sponsored project to a vote -- as outlined in the OpenSolaris Constitution -- so here are the details for the new Project, as prepared by the Project Team: Name : Erlang DTrace Integration

hi folks we''re in final approach with Brendan''s work on the TCP and UDP providers, which have been discussed here previously in the context of the overall networking provider plan at: http://hub.opensolaris.org/bin/view/Community+Group+dtrace/NetworkProvider The specs have been updated to reflect recent changes and are available for review here:

Hi, I have got an implementation of DTrace probes for NFS v3 client. Webrev of my change is at: http://cr.opensolaris.org/~danhua/webrev/ The provider and probes are described in attached proposal. Welcome comments! Regards, Danhua -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: proposal-nfsv3client.txt URL:

Is there a list anywhere of the DTrace FBT provider calls for each version of Solaris since the Nevada build that hosed the DTrace Toolkit. I have no issue with rewriting what I need, but I am hoping to stave off having to look at all the source code to find everything. I know there is a new provider under development, but I need to be able to program DTrace routines for all the updates in

I would like to request approval of the the DTrace proposal for the COMSTAR iSCSI target port provider. I have updated the specification of the iscsi provider at http://wikis.sun.com/display/DTrace/iscsi+Provider. Your feedback is appreciated. thanks Priya -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: iscsit_dtrace_draftv8.txt URL:

The iscsit_dtrace_draftv5.txt describes the Dtrace probes definition for the COMSTAR iSCSI target port provider. For all those interested in iSCSI, please take a look and send me your feedback/questions/suggestions etc by Thursday, April 20, 2009 thanks Priya -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: iscsit_dtrace_draftv5.txt URL:

We started seeing odd behaviour with clients somehow hammering our ZFS-based NFS server. Nothing is obvious from mpstat/iostat/etc. I''ve seen mention before of NFSv3 client dtrace scripts, and I was wondering if there ever was one for the server end, displaying top talkers, writes/reads, or locations of such to nail down abusive clients short of using snoop/tcpdump to nail down via

Just showing someone how great DTrace is and then we spot something I do not understand. Of course it can be a major misunderstanding of myself. Would appreciate another (expert) look upon this. The goal we try to achieve is trying to get insight if there is a bursty nature in the time slot when system calls are done. Following DTrace snippet is tried: dtrace -q -p 3173 -n

Hi, I would like to know why dtrace -l |grep plockstat show plockstat28099 lines. Process with pid 28099 is a java process. Why can I not examine other processes with the plockstat provider? Is it a java startup option? Regards Hans -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hey, Do you guys think that is a good idea to have a manual page for each provider with a complete description of what probes are offered ? Found some already under 7D category: dtrace dtrace (7d) - DTrace dynamic tracing facility fasttrap fasttrap (7d) - DTrace user instruction tracing provider fbt fbt (7d) - DTrace function boundary tracing provider

Have you considered the mdb dcmd ::pfiles? mfe at inker:~/Code/dtrace/examples$ *pfexec mdb -k* Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs ip hook neti sockfs arp usba uhci fctl s1394 stmf stmf_sbd md lofs random idm sd crypto fcp cpc fcip smbsrv nfs ufs logindmux ptm nsmb sppp nsctl sdbc rdc sv ii ipc ] > *::ps ! grep clock-applet* R 1744

Hello Srikant - A quantization distributes the results of your aggregation into ranges ordered by a power-of-two. Presumably what you''d do in your script is capture the inclusive elapsed time of each function call in your library, then use this quantization to see how tightly-banded the times are. Perhaps there''s some blocking I/O in some of your calls, for example, in which

Hi All, I used the following script from the dtrace manual to measure how long a particular process runs on the cpu. Modified it to look at the exact timestamps: [i] sched:::on-cpu { self->ts = timestamp; printf("on=%d\n", self->ts) } sched:::off-cpu /self->ts/ { printf("off=%d\n", timestamp) self->ts = 0; } [/i] The output looks like this: [i]on=24591 off=24603

As noted on my blog and at http://www.opensolaris.org/os/community/dtrace/shells/ I''ve made available a DTrace provider for the Bourne shell. Before anyone starts yelling at me for not starting with another shell, read the blog I made explaining why we started with shell (link on the community page referenced above). For /bin/sh, I''ve put up something akin to a chapter in