From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, linux-nfs@vger.kernel.org
Subject: Re: 2.6.24: RPC: bad TCP reclen 0x00020090 (large)
Date: Fri, 14 Mar 2008 20:10:14 -0400 [thread overview]
Message-ID: <20080315001014.GT2119@fieldses.org> (raw)
In-Reply-To: <C4003B51.3BE6A%tom@opengridcomputing.com>
On Fri, Mar 14, 2008 at 02:25:21PM -0500, Tom Tucker wrote:
>
> Michael:
>
> Thanks for the update. BTW, the perfect "positive fix indication" would be
> seeing a single "...bad TCP reclen..." message in the log for the
> reconnecting/confused client.
Hm. This may be entirely unrelated (and not at all your responsibility)
but
./testserver.py server:/ --rundeps -v WRT5
with newpynfs:
http://www.citi.umich.edu/projects/nfsv4/pynfs/
gets me a "RPC: bad TCP reclen 0x00000800 (non-terminal)" and a test
failure. Hm. It may be that newpynfs is doing something intolerably
weird and the server's just dropping the request instead of returning an
error. OK, probably totally unrelated. I haven't looked hard enough
yet.
--b.
next prev parent reply other threads:[~2008-03-15 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 17:28 2.6.24: RPC: bad TCP reclen 0x00020090 (large) Tom Tucker
2008-03-14 18:57 ` Michael Tokarev
[not found] ` <47DACA7C.8020807-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2008-03-14 19:06 ` J. Bruce Fields
2008-03-14 19:25 ` Tom Tucker
2008-03-15 0:10 ` J. Bruce Fields [this message]
[not found] <47B2F88D.7080300@msgid.tls.msk.ru>
[not found] ` <47B2F88D.7080300-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2008-02-18 12:58 ` Andrew Morton
2008-02-18 13:05 ` Michael Tokarev
2008-02-18 21:25 ` Tom Tucker
[not found] ` <1203369909.24272.44.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-02-18 22:00 ` Tom Tucker
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=20080315001014.GT2119@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=tom@opengridcomputing.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