All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: jin zhencheng <zhenchengjin@gmail.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	zhenchengjin@163.com
Subject: Re: nfs-error-RPC: multiple fragments per record not supported
Date: Wed, 20 Jan 2010 23:26:52 +0800	[thread overview]
Message-ID: <20100120152652.GA3595@hack> (raw)
In-Reply-To: <de04351e1001200320y2e763680gc7e3b20319c6386e@mail.gmail.com>

On Wed, Jan 20, 2010 at 07:20:34PM +0800, jin zhencheng wrote:
>I use kernel 2.6.26.2
>
>I use  29 clients,
>
>every client mount parameters as this: mount -t nfs -o
>rw,noatime,v3,rsize=32768,wsize=32768,hard,intr,tcp,nolock
>
>my system have many errors lke these :
>
>RPC: multiple fragments per record not supported
>RPC: multiple fragments per record not supported
>RPC: fragment too large: 0x318c87ee
>RPC: multiple fragments per record not supported
>RPC: fragment too large: 0x78bdeedb
>RPC: multiple fragments per record not supported
>RPC: fragment too large: 0x75cf8a33
>RPC: fragment too large: 0x44764ada
>RPC: multiple fragments per record not supported
>RPC: fragment too large: 0x0a08e7c0
>RPC: multiple fragments per record not supported
>RPC: multiple fragments per record not supported
>RPC: fragment too large: 0x5b4e13a1
>RPC: fragment too large: 0x08351a9f
>

Does 'ethtool -K eth0 tso off' help?

-- 
Live like a child, think like the god.
 

  reply	other threads:[~2010-01-20 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 11:20 nfs-error-RPC: multiple fragments per record not supported jin zhencheng
2010-01-20 11:20 ` jin zhencheng
2010-01-20 15:26 ` Américo Wang [this message]
2010-01-22  3:07   ` jin zhencheng
2010-01-22  3:07     ` jin zhencheng

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=20100120152652.GA3595@hack \
    --to=xiyou.wangcong@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=zhenchengjin@163.com \
    --cc=zhenchengjin@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 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.