When was the last time nfs_hist -z was run?
nfs_hist is good for spotting the one or two out of a couple billion read calls, but it has to be zeroed to make it more targeted.
Also there's stats.
stats show -i 1 -n 10 -r volume:oraclevol:nfs_read_latency
or if you are more interested in nfs
stats show nfsv3:nfs:nfsv3_nonblockop_latency nfsv3:nfs:nfsv3_blockop_latency nfsv3:nfs:nfsv3_op_latency
Its a long list, but easily parsed and popped into a rrd graph for historical monitoring, as opposed to nfs_hist.
Hope that helps, -Blake
On 3/14/07, Willeke, Jochen Jochen.Willeke@wincor-nixdorf.com wrote:
Hi Toasters,
we have a database on nfs space and i wonder about the output of nfs_hist.
v3 read: 35280016 (blocking requests) - millisecond units 0 1 2 3 4 5 6 7 17347681 2028005 655821 757932 1061542 1463375 1943351 1721450 <16 <24 <32 <40 <48 <56 <64 UNUSED 6417253 1334072 338371 111465 43542 18991 10063 0 <128 <192 <256 <320 <384 <448 <512 UNUSED 20806 2364 1282 617 526 280 266 0 <1024 <1536 <2048 <2560 <3072 <3584 <4096 UNUSED 723 158 77 3 0 0 0 0 <8192 <12288 <16384 <20480 <24576 <28672 <32768 UNUSED 0 0 0 0 0 0 0 0 <65536 <98304 <131072 <163840 <196608 <229376 <262144 >262144 0 0 0 0 0 0 0 0
Is the amount of read-calls with a RTT greater than 7ms ok, or is it something i have to wonder about?? I mean, the calls between 7-16ms are about 18%. But on the other hand nfs_hist shows only the blocking requests so the percentage of total calls will be even less than 18%.
Does my nfs_hist look like a healthy system or do i have a problem?
Regards and thanks for every answer :D
Jochen