From: Jose Santiago <jsantiago@chrysalisdev.com>
To: nfs@lists.sourceforge.net
Subject: RPC request reserved 240 but used 244
Date: Mon, 23 Sep 2002 08:24:37 -0500 [thread overview]
Message-ID: <3D8F1615.5000606@chrysalisdev.com> (raw)
I am seeing messages similar to the following in my kernel log since I
upgraded to 2.4.19. I have installed Trond's NFS_ALL patches and the
linux-2.4.19-30-neilb.dif patch from Trond's NFS patches site. Is this
something I need to worry about?
-------------------------------------------------------
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 reply other threads:[~2002-09-23 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 13:24 Jose Santiago [this message]
2002-09-24 4:34 ` RPC request reserved 240 but used 244 Neil Brown
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=3D8F1615.5000606@chrysalisdev.com \
--to=jsantiago@chrysalisdev.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 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.