From: Simon Kirby <sim@hostway.ca>
To: linux-nfs@vger.kernel.org
Subject: RPC: multiple fragments per record not supported
Date: Mon, 8 Jun 2009 17:20:33 -0700 [thread overview]
Message-ID: <20090609002033.GL21174@hostway.ca> (raw)
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.
Cheers,
Simon-
next reply other threads:[~2009-06-09 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 0:20 Simon Kirby [this message]
2009-06-09 2:03 ` RPC: multiple fragments per record not supported NeilBrown
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=20090609002033.GL21174@hostway.ca \
--to=sim@hostway.ca \
--cc=linux-nfs@vger.kernel.org \
/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