Linux NFS development
 help / color / mirror / Atom feed
From: Dan Yocum <yocum@fnal.gov>
To: nfs list <nfs@lists.sourceforge.net>
Subject: RPC: Unable to allocate resbuf from cache! - revisited
Date: Fri, 03 Jan 2003 09:06:48 -0600	[thread overview]
Message-ID: <3E15A708.50102@fnal.gov> (raw)

Hi all,

Looking back at the archives=20
(http://marc.theaimsgroup.com/?t=3D101707335800002&r=3D1&w=3D2) I see tha=
t you=20
(Trond) say that these copious "RPC: Unable..." messages shouldn't be a=20
problem.  Could they be a problem?

The reason I ask is, occassionally, we're getting these strange files=20
created with 0 size, date, and some gobble-dee-gook names, and they just =
so=20
happen to show up when we get this error message in the logs.  Here's wha=
t=20
one looks like:

bash-2.04$ ls -l |egrep -v '(fit|ps|fp|mem)'
total 5742612
-rwxr-xr-x    1 jen_a    sdss            0 Dec 31  1969
:N=A8TL8=D5 =E4=F0=FF=FF=EB=FE=FF=F5@                                    =
  =A6,

The rest of the files are OK, but this is slightly disconcerting.

This is 2.4.18 + XFS + NFS_ALL - rpc_tweaks, IIRC (it's been a long time =

since I've built this kernel). The system has 2GB RAM and 4GB swap (himem=
 is=20
  enabled).

Any thoughts?

Thanks,
Dan



--=20
Dan Yocum
Sloan Digital Sky Survey, Fermilab  630.840.6509
yocum@fnal.gov, http://www.sdss.org
SDSS.  Mapping the Universe.



-------------------------------------------------------
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

             reply	other threads:[~2003-01-03 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 15:06 Dan Yocum [this message]
2003-01-06  8:38 ` RPC: Unable to allocate resbuf from cache! - revisited Trond Myklebust
2003-01-06 16:29   ` Dan Yocum

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=3E15A708.50102@fnal.gov \
    --to=yocum@fnal.gov \
    --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