From: Thorsten Kranzkowski <dl8bcu@dl8bcu.de>
To: Neil Brown <neilb@suse.de>
Cc: Phy Prabab <phyprabab@gmail.com>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Odd log message associated with NFS
Date: Wed, 28 Mar 2007 18:55:34 +0000 [thread overview]
Message-ID: <20070328185534.GA585@ds20.borg.net> (raw)
In-Reply-To: <17929.53448.506302.615732@notabene.brown>
On Wed, Mar 28, 2007 at 12:19:52PM +1000, Neil Brown wrote:
> On Tuesday March 27, dl8bcu@dl8bcu.de wrote:
> > On Tue, Mar 27, 2007 at 11:40:48AM -0700, Phy Prabab wrote:
> > > kernel: rpcsvc: received unknown control message:-2144992132/-1
> >
> > Just a 'me, too':
>
> For the 'unknown control message' messages,
> see: "fix typo in svc_udp_recvfrom" previously on
> nfs@lists.sourceforge.net.
>
> Fix is in -mm and below.
will try, thanks.
> For "svc: bad direction" .... Don't know... garbage on the net maybe?
> Or maybe not. I have seen something like that before, but haven't
I don't think so as it would mean corruption at other places, too. The
Network is quite uninteresting: single ethernet segment, 2 switches
involved, longest cable 8 meters ...
> been able to pin it on anything yet.
> NeilBrown
I _had_ problems with the previous kernel (same version, same config,
different (older) compiler (gcc 3.4.5 instead of 4.1.2), on both client and server)
It would randomly (usually within 30 mins) 'lock up' NFS, where the client
sends out requests but doesn't get any answer (apart from tcp-ack) from the
server. Only a forced umount/remount recovered that (until the next lock-up).
But I'm willing to attribute that to a somehow broken gcc.
again, thanks for commenting.
bye,
Thorsten
> --- linux-2.6.orig/net/sunrpc/svcsock.c
> +++ linux-2.6/net/sunrpc/svcsock.c
> @@ -779,7 +779,7 @@ svc_udp_recvfrom(struct svc_rqst *rqstp)
> }
>
> clear_bit(SK_DATA, &svsk->sk_flags);
> - while ((err == kernel_recvmsg(svsk->sk_sock, &msg, NULL,
> + while ((err = kernel_recvmsg(svsk->sk_sock, &msg, NULL,
> 0, 0, MSG_PEEK | MSG_DONTWAIT)) < 0 ||
> (skb = skb_recv_datagram(svsk->sk_sk, 0, 1, &err)) == NULL) {
> if (err == -EAGAIN) {
>
>
> >
> > Mar 16 16:57:06 Marvin kernel: svc: bad direction 268435456, dropping request
> > Mar 16 17:58:19 Marvin kernel: svc: bad direction 268435456, dropping request
> > Mar 16 19:55:49 Marvin kernel: svc: bad direction 268435456, dropping request
> > ...
> > Mar 17 04:30:03 Marvin kernel: svc: bad direction 268435456, dropping request
--
| Thorsten Kranzkowski Internet: dl8bcu@dl8bcu.de |
| Mobile: ++49 170 1876134 Snail: Kiebitzstr. 14, 49324 Melle, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, dl8bcu@marvin.dl8bcu.ampr.org [44.130.8.19] |
next prev parent reply other threads:[~2007-03-28 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 18:40 Odd log message associated with NFS Phy Prabab
2007-03-27 19:39 ` Thorsten Kranzkowski
2007-03-28 2:19 ` Neil Brown
2007-03-28 18:55 ` Thorsten Kranzkowski [this message]
2007-03-28 16:59 ` J. Bruce Fields
2007-03-28 19:05 ` Thorsten Kranzkowski
2007-03-28 23:23 ` J. Bruce Fields
2007-03-30 20:51 ` Thorsten Kranzkowski
2007-03-30 21:03 ` J. Bruce Fields
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=20070328185534.GA585@ds20.borg.net \
--to=dl8bcu@dl8bcu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=phyprabab@gmail.com \
/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