Linux NFS development
 help / color / mirror / Atom feed
From: "Jeff L. Smith" <jeff@atheros.com>
To: nfs@lists.sourceforge.net
Subject: Vaguely NFS related problem
Date: Wed, 11 Dec 2002 17:47:00 -0800	[thread overview]
Message-ID: <3DF7EA94.20108@atheros.com> (raw)

We have been running a couple of machines (PIII with Mylex Extreme 2000 
SCSI RAID, RH7.3, 2.4.18 kernel, 64 nfsd's) which only act as NFS 
fileservers.  When either of these servers start getting busy, I start 
seeing a lot of the following messages:

Dec  8 15:27:58 localhost kernel: RPC: Unable to allocate resbuf from cache!

I does not seem to cause any problems (things keep running with no 
obvious corruption) but this surly cannot be good.  Is there something I 
need to tune or a FAQ I could review?

Jeff


-- 
Jeff Smith                                  Atheros Communications, Inc.
Hardware Manager                            529 Almanor Avenue
(408) 773-5257                              Sunnyvale, CA  94086



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2002-12-12  1:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12  1:47 Jeff L. Smith [this message]
2002-12-12  2:12 ` Vaguely NFS related problem Neil Brown
2002-12-12  2:37   ` Jeff L. Smith
2002-12-12  3:00     ` Neil Brown
2002-12-12 17:09       ` Jeff L. Smith
2002-12-13 14:07         ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2002-12-12  2:41 Jeff L. Smith

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=3DF7EA94.20108@atheros.com \
    --to=jeff@atheros.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