From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dan Yocum <yocum@fnal.gov>
Cc: nfs list <nfs@lists.sourceforge.net>
Subject: Re: RPC: Unable to allocate resbuf from cache! - revisited
Date: 06 Jan 2003 09:38:14 +0100 [thread overview]
Message-ID: <shslm1ysmfd.fsf@charged.uio.no> (raw)
In-Reply-To: <3E15A708.50102@fnal.gov>
>>>>> " " =3D=3D Dan Yocum <yocum@fnal.gov> writes:
> Hi all, Looking back at the archives
> (http://marc.theaimsgroup.com/?t=3D101707335800002&r=3D1&w=3D2) I see
> that you (Trond) say that these copious "RPC: Unable..."=20
> messages shouldn't be a problem. Could they be a problem?
> The reason I ask is, occassionally, we're getting these strange
> files created with 0 size, date, and some gobble-dee-gook
> names, and they just so happen to show up when we get this
> error message in the logs. Here's what 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.
That's totally unrelated to the above message, and looks rather like a
server bug. Is the server also 2.4.18+XFS?
Cheers,
Trond
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-01-06 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 15:06 RPC: Unable to allocate resbuf from cache! - revisited Dan Yocum
2003-01-06 8:38 ` Trond Myklebust [this message]
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=shslm1ysmfd.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=yocum@fnal.gov \
/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