From: Steve Dickson <SteveD@redhat.com>
To: sreya <m_sreya@yahoo.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: how to interpret 'nfsstat' ouput
Date: Thu, 18 Sep 2003 09:53:20 -0400 [thread overview]
Message-ID: <3F69B8D0.3090105@RedHat.com> (raw)
In-Reply-To: <20030918061313.58617.qmail@web13108.mail.yahoo.com>
sreya wrote:
>hi,
>Iam trying to trace NFS output to determine the health
>of NFS. CAn anyone please tell me how to interpret the
>NFS statistics and decide the condition of NFS i.e,
>whether the NFS server is not working or NFS is about
>to die etc.
>I want to know the statistics on the server side
>without any intervention of the clients present.
>
what's wrong with doing a nfsstat -s (on the server) and
the noting the rpc calls count?
SteveD.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-09-18 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 6:13 how to interpret 'nfsstat' ouput sreya
2003-09-18 13:53 ` Steve Dickson [this message]
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=3F69B8D0.3090105@RedHat.com \
--to=steved@redhat.com \
--cc=m_sreya@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox