Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

Hello Jim! Actually i can repeat it... every time i did run some d script to collect some data i got some (how do you call it? nasty :) values. Look: Fri Dec 5 10:19:32 BRST 2008 Fri Dec 5 10:29:34 BRST 2008 NFSv3 read/write distributions (us): read value -

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

HmmmSomething is certainly wrong. 11 writes at 137k - 275k seconds (which is where your 1.5M seconds sum is coming from) is bogus. What version of Solaris is this ('uname -a' and 'cat /etc/release')? Your running this on an NFS server, right (not client)? Is this a benchmark? I ask because

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

Hello Jim, this is not a benchmark. The filenames i did change for privacy... This is a NFS server, yes. # uname -a SunOS test 5.11 snv_89 i86pc i386 i86pc # cat /etc/release Solaris Express Community Edition snv_89 X86 Copyright 2008 Sun Microsystems, Inc. All

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

Also (I meant to ask) - are you having performance problems, or just monitoring with the NFS provider scripts? Thanks, /jim Marcelo Leal wrote: Hello Jim, this is not a benchmark. The filenames i did change for privacy... This is a NFS server, yes. # uname -a SunOS test 5.11 snv_89 i86pc

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

Hi, I have looked at the script, and there is no correspondence between start and done. So, I am not sure how this script is supposed to work. I think there should be a predicate in the done probes... The way the script is written, it assumes that for any start, the done that fires after it is

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

Oops, that would be a nice test, but something i cannot do. ;-) [http://www.eall.com.br/blog] Leal. -- This message posted from opensolaris.org ___ dtrace-discuss mailing list dtrace-discuss@opensolaris.org

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

Some kind of both... ;-) I was investigating a possible performance problem, that i'm not sure if is the NFS server or not. So, i was faced with that weird numbers. I think one thing is not related with the other, but we need to fix whatever is the problem with the script or the provider, to

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

D'oh! Good spot Max - feeling sheepish that I missed that. Marcelo - add the predicate to the done probes as per Max's message, and let's see where that takes us Thanks, /jim [EMAIL PROTECTED] wrote: Hi, I have looked at the script, and there is no correspondence between start and

Re: [dtrace-discuss] Is the nfs dtrace script right (from nfsv3 provider wiki)?

On Tue, Dec 09, 2008 at 05:04:49PM +0100, [EMAIL PROTECTED] wrote: Hi, I have looked at the script, and there is no correspondence between start and done. So, I am not sure how this script is supposed to work. I think there should be a predicate in the done probes... The way the script is

Re: [dtrace-discuss] Trying to identify writer and/or reason for iowrite.

On Fri, Dec 05, 2008 at 05:15:09PM -0500, Jim Mauro wrote: The problem you're running into is disk IO operations tend to occur asynchronously to the thread that initiated the IO, so when the IO provider probe fires, execname shows the process name for PID 0. This is not uncommon when chasing