All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Elliott Finley <finley@anl.gov>
To: Reuti <reuti@staff.uni-marburg.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: rpc.mountd at 99% cpu
Date: Thu, 29 Sep 2005 15:09:21 -0500	[thread overview]
Message-ID: <433C49F1.1010409@anl.gov> (raw)
In-Reply-To: <20050929215204.85kt3qx0hwf4kc00@home.staff.uni-marburg.de>

Reuti,

/proc/fs/nfsd/ does exist.  I'll go back and have a look at your posts.

-Brian



Reuti wrote:

> Typo: the one I meant was /proc/fs/nfsd - is there anything in this
> directory?
>
> -- Reuti
>
> Zitat von Brian Elliott Finley <finley@anl.gov>:
>
> > Reuti,
> >
> > Thanks for your reply, but I'm afraid /proc/nfs/nfsd is *not* currently
> > mounted.
> >
> > Cheers, -Brian
> >
> >
> > Reuti wrote:
> >
> >> Brian,
> >>
> >> is there a file system mounted in /proc/nfs/nfsd - then nfsd is working
> >> in a new
> >> mode? You can try *not* to mount it in the start/stop-script of the NFS
> >> server.
> >> This way you will force nsfd to operate in a legacy mode. If you
> >> followed my
> >> posts last week, this solved a problem with stale file handles for me.
> >>
> >> Cheers - Reuti
> >>
> >>
> >> Zitat von Brian Elliott Finley <finley@anl.gov>:
> >>
> >> > I've got an nfs server (quad cpu amd64, 36G mem, failover
> fiberchannel)
> >> > running ubuntu, and I'm getting the following behavior that I haven't
> >> > been able to track down yet:
> >> >
> >> >    * rpc.mountd spikes to 99% cpu usage when a client machine mounts,
> >> >      causing a temporary disruption in service to all client systems
> >> >
> >> > Google, NFS Howtos, NFS Perf Tuning docs, IRC (can't find an NFS
> >> > specific IRC channel), local sysadmins all turn up nothing so
> far.  Here
> >> > are potentially relavant data:
> >> >
> >> >    * exportfs -v -o rw,secure,sync,no_root_squash
> >> >      10.10.0.0/255.255.0.0:/export/home
> >> >    * nfs server has all clients info in /etc/hosts
> >> >    * /etc/hosts is first in nsswitch.conf
> >> >    * kernel is ubuntu's: linux-image-2.6.10-5-amd64-k8-smp
> >> >    * nfs performance is fine once a filesystem is mounted
> >> >    * unless, someone else is mounting a filesystem, in which case
> >> >      already mounted filesystems
> >> >    * only 8 clients
> >> >    * home directories mounted by autofs on clients as
> >> >      server:/export/home/bob /home/bob
> >> >    * 32 nfsd threads
> >> >    * % netstat -in
> >> >      Kernel Interface table
> >> >      Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR   TX-OK TX-ERR
> TX-DRP
> >> >      TX-OVR Flg
> >> >      eth0   1500 0  247854230      0      0      0324570001      0
> >> >      0      0 BMRU
> >> >      eth1   1500 0  1022171197      0      0      0258643880
> >> >      0      0      0 BMR U
> >> >      lo    16436 0    419024      0      0      0  419024      0
> >> >      0      0 LRU
> >> >    * % cat /proc/net/rpc/nfsd | grep ^th
> >> >      th 32 8229 13759.142 6537.314 1919.479 4.212 129.977 52.636
> 11.780
> >> >      10.231 0.000 101.321
> >> >    * caching bind9 installed on server, and it points to itself for
> >> >      first nameserver entry
> >> >
> >> > Any one know what's up here?  Or how I can tell what's making
> rpc.mountd
> >> > take so much time?
> >> >
> >> > --
> >> > Brian Elliott Finley
> >> > Linux Strategist, CIS
> >> > Desk: 630.252.4742
> >> > Cell: 630.631.6621
> >> >
> >> >
> >> >
> >> > -------------------------------------------------------
> >> > This SF.Net email is sponsored by:
> >> > Power Architecture Resource Center: Free content, downloads,
> >> discussions,
> >> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> >> > _______________________________________________
> >> > NFS maillist  -  NFS@lists.sourceforge.net
> >> > https://lists.sourceforge.net/lists/listinfo/nfs
> >> >
> >>
> >>
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.Net email is sponsored by:
> >> Power Architecture Resource Center: Free content, downloads,
> discussions,
> >> and more. http://solutions.newsforge.com/ibmarch.tmpl
> >> _______________________________________________
> >> NFS maillist  -  NFS@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/nfs
> >>
> >
> > --
> > Brian Elliott Finley
> > Linux Strategist, CIS
> > Desk: 630.252.4742
> > Cell: 630.631.6621
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,
> discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > NFS maillist  -  NFS@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs
> >
>

-- 
Brian Elliott Finley
Linux Strategist, CIS
Desk: 630.252.4742
Cell: 630.631.6621



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-09-29 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 19:12 rpc.mountd at 99% cpu Brian Elliott Finley
2005-09-29 19:35 ` Reuti
2005-09-29 19:42   ` Brian Elliott Finley
2005-09-29 19:52     ` Reuti
2005-09-29 20:09       ` Brian Elliott Finley [this message]
2005-09-29 20:17         ` Brian Elliott Finley
2005-09-29 20:31           ` Reuti
2005-09-29 21:46             ` Brian Elliott Finley
2005-09-30 21:41               ` Brian Elliott Finley

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=433C49F1.1010409@anl.gov \
    --to=finley@anl.gov \
    --cc=nfs@lists.sourceforge.net \
    --cc=reuti@staff.uni-marburg.de \
    /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.