From: "NeilBrown" <neilb@suse.de>
To: "Simon Kirby" <sim@hostway.ca>
Cc: linux-nfs@vger.kernel.org
Subject: Re: RPC: multiple fragments per record not supported
Date: Tue, 9 Jun 2009 12:03:42 +1000 (EST) [thread overview]
Message-ID: <676fa8ce48993d133dc0c5deb308ea14.squirrel@neil.brown.name> (raw)
In-Reply-To: <20090609002033.GL21174@hostway.ca>
On Tue, June 9, 2009 10:20 am, Simon Kirby wrote:
> Hello!
>
> With 2.6.28.10 and 2.6.29.4 knfsd after a few hours of heavy concurrent
> NFSv3 write loads (migration of Maildirs with rsync), we are seeing this
> error:
>
> kernel: RPC: multiple fragments per record not supported
>
> ...followed by knfsd immediately ignoring all further requests.
> Restarting knfsd (/etc/init.d/nfs-kernel-server restart) seems to make
> it start responding and work as normal again.
>
> "ps -eo pid,stat,args,wchan" during the event shows all nfsd processes
> sleeping in "svc_recv":
>
> 22714 S< [nfsd] svc_recv
>
> This client with the high write load is an old 2.6.17 kernel, mounting
> the server with
> rw,nolock,hard,intr,timeo=9,retrans=3,rsize=8192,wsize=8192
> (jumbo frames are enabled).
>
> Is this any sort of known issue? I'm trying to reproduce it in a testing
> environment.
Yes. Known issue. The data stream from the client gets corrupted.
Fix is
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e0ab53deaa91293a7958d63d5a2cf4c5645ad6f0
which is in 2.6.18
NeilBrown
prev parent reply other threads:[~2009-06-09 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 0:20 RPC: multiple fragments per record not supported Simon Kirby
2009-06-09 2:03 ` NeilBrown [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=676fa8ce48993d133dc0c5deb308ea14.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=sim@hostway.ca \
/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