All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jehan PROCACCIA <Jehan.Procaccia@int-evry.fr>
To: nfs@lists.sourceforge.net
Subject: interprtation of /proc/net/rpc/nfsd
Date: Fri, 08 Oct 2004 12:09:59 +0200	[thread overview]
Message-ID: <41666777.7030003@int-evry.fr> (raw)

Hello,

I am tunning my NFS configuration on a RedHat ES v3 (equivalent Fedora 
Core 1 , kernel 2.4.X)  and by reading the docs (NFS howto perf 5.6 )  I 
should see if I have enough NFSD daemon by looking at  
/proc/net/rpc/nfs, especialy line "th"

$ grep th /proc/net/rpc/nfsd
th 8 41598 20357.020 3974.540 1809.300 0.000 998.210 781.650 483.840 
116.640 0.000 825.230

However I cannot understand how to read that information !?
I see that I have 8 threads (8 nfsd daemon runing) but figures after ???

Second question,

How on an NFS client (Here I have fedora core 2 clients) can I see how 
is currently mounted an NFS filsystem, I want to check what are the 
current options in use (nfs version, rsize, wsize, sync/async, hard, 
soft etc ...). On the server I can have a look at /var/lib/nfs/xtab

$ cat /var/lib/nfs/xtab | grep arvouin
/mci/mci        
arvouin.int-evry.fr(rw,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,subtree_check,secure_locks,acl,mapping=identity,anonuid=-2,anongid=-2)

but I am often changing options on the server (for tunning purpose) , 
and hence I want to check that my clients is mounted with the latest 
options,  do I need to remount on the client everytime I change options 
on the server ? (exportfs -r -v -a)  ... .checking what is the current 
options on the client would be more clear to me .

thanks.

PS other lines are also not clear in /proc/net/rpc/nfsd
are they clearly explain somewhere ? or is there a better tool to read 
them ?

$ cat /proc/net/rpc/nfsd
rc 77 2279806 4791576
fh 36 7103818 0 107 461
io 2157379507 3834347693
th 8 41598 20368.720 3975.220 1809.300 0.000 998.210 781.650 483.840 
116.640 0.000 825.230
ra 16 316291 228 80 73 25 40 42 17 36 7 22131
net 7071459 56823 7014636 155
rpc 7071459 0 0 0 0
proc2 18 95 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc3 22 107 2606933 544561 626398 870018 178 338970 1189408 253948 
14640 200 0 219018 12808 45181 119 0 66482 4981 22 0 277392




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2004-10-08 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 10:09 Jehan PROCACCIA [this message]
2004-10-08 13:03 ` interprtation of /proc/net/rpc/nfsd James Pearson
2004-10-08 13:28   ` Jehan PROCACCIA
2004-10-08 14:43     ` James Pearson
2004-10-08 15:46       ` Jehan PROCACCIA
2004-10-11 11:13         ` Steve Dickson
2004-10-11 13:01           ` Jehan PROCACCIA
  -- strict thread matches above, loose matches on Subject: below --
2004-10-11 15:22 Lever, Charles
2004-10-12  9:05 ` Steve Dickson

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=41666777.7030003@int-evry.fr \
    --to=jehan.procaccia@int-evry.fr \
    --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.