All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Timo Rothenpieler <timo@rothenpieler.org>
Cc: Leon Romanovsky <leon@kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: NFS over RDMA issues on Linux 5.4
Date: Tue, 4 Aug 2020 11:46:41 -0400	[thread overview]
Message-ID: <4751E7F5-AAB1-4602-B926-9BB08E1D213D@oracle.com> (raw)
In-Reply-To: <7c7418cb-7f7a-5de3-2025-7bde5cd5ac2a@rothenpieler.org>



> On Aug 4, 2020, at 11:39 AM, Timo Rothenpieler <timo@rothenpieler.org> wrote:
> 
> On 04.08.2020 17:34, Chuck Lever wrote:
>> I see a LOC_LEN_ERR on a Receive. Leon, doesn't that mean the server's
>> Send was too large?
>> Timo, what filesystem are you sharing on your NFS server? The thing that
>> comes to mind is https://bugzilla.kernel.org/show_bug.cgi?id=198053
> 
> The filesystem on the server is indeed a zfs-on-linux (version 0.8.4), just as in that bug report.
> 
> Should I try to apply the proposed fix you posted on that bug report on the client (and server?).

If you are hitting that bug, the server is the problem. The client
should work fine once the server is fixed. (I'm not happy about
the client's looping behavior either, but that will go away once
the server behaves).

I'm not hopeful that the fix applies cleanly to v4.19, but it
might. Another option would be upgrading your NFS server.


--
Chuck Lever




  reply	other threads:[~2020-08-04 15:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 15:05 NFS over RDMA issues on Linux 5.4 Timo Rothenpieler
2020-08-03 16:24 ` Chuck Lever
2020-08-04  9:36   ` Leon Romanovsky
2020-08-04 10:52     ` Timo Rothenpieler
2020-08-04 12:25       ` Leon Romanovsky
2020-08-04 12:49         ` Chuck Lever
2020-08-04 13:08           ` Timo Rothenpieler
2020-08-04 13:12             ` Chuck Lever
2020-08-04 13:19               ` Timo Rothenpieler
2020-08-04 13:24                 ` Chuck Lever
2020-08-04 13:40                   ` Timo Rothenpieler
2020-08-04 13:46               ` Leon Romanovsky
2020-08-04 13:53                 ` Chuck Lever
2020-08-04 15:34                   ` Chuck Lever
2020-08-04 15:39                     ` Timo Rothenpieler
2020-08-04 15:46                       ` Chuck Lever [this message]
2020-08-04 15:50                         ` Timo Rothenpieler
2020-08-04 16:07                           ` Timo Rothenpieler
2020-08-04 15:55                     ` Leon Romanovsky

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=4751E7F5-AAB1-4602-B926-9BB08E1D213D@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=leon@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=timo@rothenpieler.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 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.