All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Boeckman <matthewb@saepio.com>
To: nfs@lists.sourceforge.net
Subject: nfsstat limitations?
Date: Mon, 25 Mar 2002 10:09:49 -0600	[thread overview]
Message-ID: <3C9F4BCD.5050404@saepio.com> (raw)

Hello list!

I'm trying to track down some information about the nfsstat on linux. 
Specifically from nfs-utils-0.3.1-5 on RH7.1 . What I'm looking for is 
some additional client RPC information. nfsstat on solaris gives me all 
kinds of nifty output about timeouts, badcalls, timers, etc:
Client rpc:
Connection oriented:
calls       badcalls    badxids     timeouts    newcreds    badverfs
0           0           0           0           0           0
timers      cantconn    nomem       interrupts
0           0           0           0
Connectionless:
calls       badcalls    retrans     badxids     timeouts    newcreds
4           1           0           0           0           0
badverfs    timers      nomem       cantsend
0           1           0           0

on linux:
Client rpc stats:
calls      retrans    authrefrsh
70163      12         0

I've read the man page and docs on the sourceforge site, and it doesn't 
appear that I'm missing any command line options. Is there somewhere 
other than nfsstat that I can get this info?

Another question along the same lines: how can I track client side NFS 
cache hit's and caching information in general? For a variety of 
reasons, I'm caching the entire mounted filesystem for a long time, and 
am interested/concerned in being able to track the system impact of 
that. Things like, of all NFS calls, how many are being answered by the 
cache, how much system resources is this cache taking up, etc. Thanks 
for any and all replies!

-Matthew


_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2002-03-25 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 16:09 Matthew Boeckman [this message]
2002-03-25 19:36 ` nfsstat limitations? Tom McNeal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C9F4BCD.5050404@saepio.com \
    --to=matthewb@saepio.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.