Linux NFS development
 help / color / mirror / Atom feed
From: Andreas Behnert <abehn@gmx.net>
To: nfs@lists.sourceforge.net
Subject: statd error messages - do I need a more recent nfs-utils version?
Date: Tue, 15 Apr 2003 17:53:21 +0200	[thread overview]
Message-ID: <3E9C2AF1.5000003@gmx.net> (raw)

Hello,

server was running Debian 3.0r1 + kernel 2.2.20 (vanilla) and
some days ago because of various reasons I had to upgrade to
kernel 2.4.x ASAP. Because of some knfsd related fixes in 2.4.21-pre
I did some stability tests and after that I installed 2.4.21-pre7
on the server. With the new kernel statd often causes error messages
in the server log, for instance:

(srv = server
  and three drifferent clients as an example:
   .105 = AIX 5.1-ML2
   .107 = HP-UX 11.0U
   .114 = IRIX 6.5.15)

~~~snip~~~
srv rpc.statd[475]: Received erroneous SM_UNMON request from srv for
  x.x.x.105
srv rpc.statd[475]: Received erroneous SM_UNMON request from srv for
  x.x.x.107
srv rpc.statd[475]: Received erroneous SM_UNMON request from srv for
  x.x.x.114
~~~snip~~~

Are these messages somehow important? With kernel 2.2.20 there were no
such messages.
Debian Woody comes with nfs-utils 1.0 - maybe these messages are related
to this older utils version and I have to update nfs-utils to 1.0.3?
Building the Debian package wouldn't be a problem ...


Regards,
Andreas



-------------------------------------------------------
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-04-15 15:53 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=3E9C2AF1.5000003@gmx.net \
    --to=abehn@gmx.net \
    --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