SCIENTIFIC-LINUX-USERS Archives

February 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Chris Schanzle <[log in to unmask]>
Reply To:
Chris Schanzle <[log in to unmask]>
Date:
Tue, 28 Feb 2012 17:05:15 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
On 02/28/2012 02:25 PM, Vladimir Mosgalin wrote:
>   On 2012.02.28 at 11:32:17 -0500, Wayne Betts wrote next:
>
>> We have a couple of Scientific Linux 6.1 NFS servers.  I looked at
>> /proc/net/rpc/nfsd and was surprised to see on both of them that
>> the thread histogram is all zero:
>>
>> # cat /proc/net/rpc/nfsd | grep th
>> th 8 0 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
>
> It is the same for me on nfs4 server on SL6.2
>
> What statistics are you trying to get? What's wrong with standard way of
> querying nfs server, "nfsstat -s" command?
> It's much better than looking in proc, because the file you see there is
> specific only to current linux kernel-mode nfs implementation, while
> nfsstat -s *is* the correct and portable way across various systems.


The "th" statistics are unique to monitoring if you have the proper # of nfsd threads running; 'nfsstat -s' can't show that.

I looked at this issue several months ago and I recall, but cannot find reference today, that the kernel developers decided the code to collect statistics was broken and they've disabled it.

That kinda stinks, since the code was *basically* functional and gave a clue.

ATOM RSS1 RSS2