From: Greg Banks <gnb@melbourne.sgi.com>
To: Marc Schmitt <mschmitt@inf.ethz.ch>
Cc: nfs@lists.sourceforge.net
Subject: Re: bad cookie size 20 (only cookies under 8 bytes are supported.)
Date: Wed, 05 Nov 2003 14:54:32 +1100 [thread overview]
Message-ID: <3FA87478.BE1069F9@melbourne.sgi.com> (raw)
In-Reply-To: 3FA512B2.1080109@inf.ethz.ch
Marc Schmitt wrote:
>
> Hi all,
>
> I did upgrade yesterday my RedHat 7.3 box (2.4.20-20.7smp) from
> nfs-utils 1.0.5 to 1.0.6, after that, messages was full with:
>
> Nov 2 15:02:56 server kernel: lockd: bad cookie size 20 (only cookies
> under 8 bytes are supported.)
> Nov 2 15:02:56 server kernel: svc: failed to decode args
> Nov 2 15:02:57 server kernel: lockd: bad cookie size 20 (only cookies
> under 8 bytes are supported.)
> Nov 2 15:02:57 server kernel: svc: failed to decode args
> Nov 2 15:03:16 server kernel: lockd: bad cookie size 20 (only cookies
> under 8 bytes are supported.)
>
> I've never had those messages before, does 1.0.6 require a certain
> minimum kernel version (ex. >= 2.4.22)?
I sent Trond a patch to fix this in March. It's not your nfs-utils,
somebody on the network started a MacOS X 10.3 NFS client.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-11-05 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 14:20 bad cookie size 20 (only cookies under 8 bytes are supported.) Marc Schmitt
2003-11-02 17:22 ` Marc Schmitt
2003-11-05 3:54 ` Greg Banks [this message]
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=3FA87478.BE1069F9@melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=mschmitt@inf.ethz.ch \
--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.