From: Neil Brown <neilb@suse.de>
To: Narayan Desai <desai@mcs.anl.gov>
Cc: nfs@lists.sourceforge.net
Subject: Re: odd kernel-nfs-server messages
Date: Wed, 7 Nov 2007 15:56:44 +1100 [thread overview]
Message-ID: <18225.17804.342785.5822@notabene.brown> (raw)
In-Reply-To: message from Narayan Desai on Tuesday November 6
On Tuesday November 6, desai@mcs.anl.gov wrote:
> We are running into some kernel nfs server errors that we are having
> trouble deciphering.
>
> We are running a x86_64 nfs server. The server is running ubuntu
> feisty, with their 2.6.20-16-generic kernel.
>
> The clients are also running linux (2.6.15 kernel; we are waiting on
> the system vendor to finish their port to a newer kernel) on mips64.
This looks a lot like the bug fixed by commit
e0ab53deaa91293a7958d63d5a2cf4c5645ad6f0
which was still present in 2.6.15 (fix in 2.6.18).
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e0ab53deaa91293a7958d63d5a2cf4c5645ad6f0
If the client gets an error sending data (because there is no buffer
space), the remainder of the packet is discard, but it keeps the same
tcp connection open. When it sends another packet, presumably when
buffer space is available, it gets sent and appears to be part of the
previous packet. Confusion ensues.
NeilBrown
>
> Under fairly heavy load (400-800 clients, not a ton of reads and
> writes) we get the following messages:
>
> [1724467.119033] RPC: bad TCP reclen 0x337e08af (large)
> [1738771.833213] RPC: bad TCP reclen 0x00000014 (non-terminal)
> [1738801.224098] RPC: bad TCP reclen 0x6d346e31 (non-terminal)
> [1738965.738860] RPC: bad TCP reclen 0x6d376e39 (non-terminal)
> [1739183.459936] RPC: bad TCP reclen 0x342e7363 (non-terminal)
> [1739295.006403] RPC: bad TCP reclen 0x73797374 (non-terminal)
> [1739383.784788] RPC: bad TCP reclen 0x00000003 (non-terminal)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-11-07 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 4:21 odd kernel-nfs-server messages Narayan Desai
2007-11-07 4:56 ` Neil Brown [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=18225.17804.342785.5822@notabene.brown \
--to=neilb@suse.de \
--cc=desai@mcs.anl.gov \
--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.