On 04.08.2020 17:50, Timo Rothenpieler wrote:
On 04.08.2020 17:46, Chuck Lever wrote:
On Aug 4, 2020, at 11:39 AM, Timo Rothenpieler
<timo@xxxxxxxxxxxxxxxx> 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.
It's running on 5.4.54 and the patch applies with no fuzz whatsoever:
I will deploy the patch to both server and client and report back.
Reporting success.
With the patch from that bug applied, no error spam is happening anymore.
Plus, the filesystem actually works and definitely got a whole lot
snappier than before. Which is not all that unexpected.
Thank you so much for your help analyzing this and for the fix!
I hope it can get applied to mainline soon and will reach 5.4 backports
eventually.
Until then, I will carry it as a local patch for the systems.
Thanks again,
Timo
