Linux NFS development
 help / color / mirror / Atom feed
From: Venkat Ram Reddy <reddy@apache-da.com>
To: nfs@lists.sourceforge.net
Subject: rpc.mountd dies under heavy load
Date: Wed, 26 Apr 2006 10:10:30 -0700	[thread overview]
Message-ID: <444FA986.7040709@apache-da.com> (raw)

Hi All,

I have a lsf farm with 20 running jobs writing data to a nfs exported 
disk. This causes high load average ( 15-20 ) on the nfs server, and 
rpc.mountd dies. What could be the problem? My nfs server is RHEL AS3.0 
AMD64 and has nfs-utils-1.0.6-42EL.

Thanks

-- 
Venkat Ram Reddy




-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2006-04-26 17:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=444FA986.7040709@apache-da.com \
    --to=reddy@apache-da.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