According to http://blogs.sun.com/brendan/entry/iscsi_dtrace_provider and
http://wikis.sun.com/display/DTrace/iscsi+Provider there should be a dtrace
provider for iscsi. However, on Solaris 10 10/08, there doesn''t seem to
be one. Should there be? If so, how do I get it enabled?
[root at sol10-1 /]# dtrace -ln ''iscsi*:::''
ID PROVIDER MODULE FUNCTION NAME
dtrace: failed to match iscsi*:::: No probe matches description
[root at sol10-1 /]# cat /etc/release
Solaris 10 10/08 s10x_u6wos_07b X86
Thanks
--
CV
--
This message posted from opensolaris.org
C V wrote:> According to http://blogs.sun.com/brendan/entry/iscsi_dtrace_provider and http://wikis.sun.com/display/DTrace/iscsi+Provider there should be a dtrace provider for iscsi. However, on Solaris 10 10/08, there doesn''t seem to be one. Should there be? If so, how do I get it enabled? > > [root at sol10-1 /]# dtrace -ln ''iscsi*:::'' > ID PROVIDER MODULE FUNCTION NAME > dtrace: failed to match iscsi*:::: No probe matches description > [root at sol10-1 /]# cat /etc/release > Solaris 10 10/08 s10x_u6wos_07b X86 > > Thanks > -- > CVIt''s not clear to me it''s in 10/08, but, on relatively-recent Nevada, that dtrace command shows no output either. I didn''t think USDT probes allowed wildcarding the PID. dtrace -ln "ksh*:::" ID PROVIDER MODULE FUNCTION NAME dtrace: failed to match ksh*:::: No probe matches description I don''t have an iscsitgtd process to try it with.
You can list USDT probes with a wildcard, as long the process is running. Is the iSCSI target daemon (iscsitgtd) running? If not, then ''dtrace -ln'' won''t list the probes. If the process is running, and the probes still don''t show up, I''d say 10/08 doesn''t have the provider. Chip
The DTrace provider for iscsi has not been ported back to S10. As far as I know there are no current plans to do so. Peter Dan Mick wrote:> C V wrote: >> According to http://blogs.sun.com/brendan/entry/iscsi_dtrace_provider >> and http://wikis.sun.com/display/DTrace/iscsi+Provider there should >> be a dtrace provider for iscsi. However, on Solaris 10 10/08, there >> doesn''t seem to be one. Should there be? If so, how do I get it enabled? >> >> [root at sol10-1 /]# dtrace -ln ''iscsi*:::'' >> ID PROVIDER MODULE FUNCTION >> NAME >> dtrace: failed to match iscsi*:::: No probe matches description >> [root at sol10-1 /]# cat /etc/release Solaris 10 >> 10/08 s10x_u6wos_07b X86 >> >> Thanks >> -- >> CV > > It''s not clear to me it''s in 10/08, but, on relatively-recent Nevada, > that dtrace command shows no output either. I didn''t think USDT > probes allowed wildcarding the PID. > > dtrace -ln "ksh*:::" > ID PROVIDER MODULE FUNCTION NAME > dtrace: failed to match ksh*:::: No probe matches description > > I don''t have an iscsitgtd process to try it with. > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org
I wonder if it would work to grab iscsitgtd from Nevada and run it in place of the one in Solaris 10. Certainly too risky for a production environment, but if you''re just playing around.... Chip Sent from my Windows Mobile? phone. -----Original Message----- From: Peter Cudhea <Peter.Cudhea at Sun.COM> Sent: Thursday, February 12, 2009 5:41 PM To: Dan Mick <Dan.Mick at Sun.COM> Cc: dtrace-discuss at opensolaris.org <dtrace-discuss at opensolaris.org>; C V <rayvittal-lists at yahoo.com> Subject: Re: [dtrace-discuss] iscsi provider The DTrace provider for iscsi has not been ported back to S10. As far as I know there are no current plans to do so. Peter Dan Mick wrote:> C V wrote: >> According to http://blogs.sun.com/brendan/entry/iscsi_dtrace_provider >> and http://wikis.sun.com/display/DTrace/iscsi+Provider there should >> be a dtrace provider for iscsi. However, on Solaris 10 10/08, there >> doesn''t seem to be one. Should there be? If so, how do I get it enabled? >> >> [root at sol10-1 /]# dtrace -ln ''iscsi*:::'' >> ID PROVIDER MODULE FUNCTION >> NAME >> dtrace: failed to match iscsi*:::: No probe matches description >> [root at sol10-1 /]# cat /etc/release Solaris 10 >> 10/08 s10x_u6wos_07b X86 >> >> Thanks >> -- >> CV > > It''s not clear to me it''s in 10/08, but, on relatively-recent Nevada, > that dtrace command shows no output either. I didn''t think USDT > probes allowed wildcarding the PID. > > dtrace -ln "ksh*:::" > ID PROVIDER MODULE FUNCTION NAME > dtrace: failed to match ksh*:::: No probe matches description > > I don''t have an iscsitgtd process to try it with. > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org_______________________________________________ dtrace-discuss mailing list dtrace-discuss at opensolaris.org
I don''t think using the Nevada iscsitgtd on S10 will work at all. It *certainly* won''t work for DTrace. A little background: The reason we *didn''t* port the iscsi provider back to S10 (as part of the recent putback of iscsi fixes to S10U7) was because the iscsi provider is inextricably dependent on the dtrace operator for printing IP addresses, inet_ntoa and inet_ntoa6. That suite of functions is part of Dtrace function level 1.5. Given the DTrace stability guarantees, you must either port all of DTrace level 1.5 or none of it. And that was beyond our charter. So until that back port gets done for some other reason, there is no iscsi provider in S10. We did thoroughly review whether there is even a marginal kind of alternate probe that could have been implemented with the resources available. We convinced ourselves nothing other than the full port of DTrace level 1.5 would be worthwhile. The truly pain-crazy can always use the pid provider to investigate iscsitgtd behavior. Peter C V wrote: I''ll try that, thanks. ----- Original Message ---- From: Chip Bennett To: Peter Cudhea ; Dan Mick Cc: dtrace-discuss-xZgeD5Kw2fzokhkdeNNY6A@public.gmane.org; C V Sent: Thursday, February 12, 2009 3:55:14 PM Subject: RE: [dtrace-discuss] iscsi provider I wonder if it would work to grab iscsitgtd from Nevada and run it in place of the one in Solaris 10. Certainly too risky for a production environment, but if you''re just playing around.... Chip Sent from my Windows Mobile® phone. -----Original Message----- From: Peter Cudhea Sent: Thursday, February 12, 2009 5:41 PM To: Dan Mick Cc: dtrace-discuss-xZgeD5Kw2fzokhkdeNNY6A@public.gmane.org ; C V Subject: Re: [dtrace-discuss] iscsi provider The DTrace provider for iscsi has not been ported back to S10. As far as I know there are no current plans to do so. Peter Dan Mick wrote: C V wrote: According to http://blogs.sun.com/brendan/entry/iscsi_dtrace_provider and http://wikis.sun.com/display/DTrace/iscsi+Provider there should be a dtrace provider for iscsi. However, on Solaris 10 10/08, there doesn''t seem to be one. Should there be? If so, how do I get it enabled? [root@sol10-1 /]# dtrace -ln ''iscsi*:::'' ID PROVIDER MODULE FUNCTION NAME dtrace: failed to match iscsi*:::: No probe matches description [root@sol10-1 /]# cat /etc/release Solaris 10 10/08 s10x_u6wos_07b X86 Thanks -- CV It''s not clear to me it''s in 10/08, but, on relatively-recent Nevada, that dtrace command shows no output either. I didn''t think USDT probes allowed wildcarding the PID. dtrace -ln "ksh*:::" ID PROVIDER MODULE FUNCTION NAME dtrace: failed to match ksh*:::: No probe matches description I don''t have an iscsitgtd process to try it with. _______________________________________________ dtrace-discuss mailing list dtrace-discuss-xZgeD5Kw2fzokhkdeNNY6A@public.gmane.org dtrace-discuss mailing list dtrace-discuss-xZgeD5Kw2fzokhkdeNNY6A@public.gmane.org