Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp421109pxa; Tue, 4 Aug 2020 08:40:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzrmV9nAdinYq8KhXbe4txqdDoRYOk4GRaFIUBB5f5UuZ+NHre4k44zrmlRTsM//X4+TFRp X-Received: by 2002:a50:ba85:: with SMTP id x5mr20163655ede.38.1596555631743; Tue, 04 Aug 2020 08:40:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596555631; cv=none; d=google.com; s=arc-20160816; b=WenmWG1lOX8u2hfX15kQLMt5+cZuWF4Uf0lboyIZU5VvRZz5djKFu+urXsZrXZnrRu pgNfyG/Ph2ugst9gcGDOttJpvL0oJMa7UMr7abaaigQ48RAvHn8fDI5q4vopNJCIqJ09 juibwoSBlS4LRI1cRdL7NGD3tFMGShYBAeSCuJIiYKY9176QvtSOvlWBJ23EJMSOUVqc 6qDfy6oaNlXJfhHaDirxd4GzFx/BuQaYGrHtzCFX3d84lkHiMVVoz5uQZbhOYPcFMfhf pE4p8v2G2rU0NUg52qTfaAUE6RrAhANyQaRDs6w5bljxVKlZeEN649ja7sXJOGD2e/vn 8z3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=ZYn5mOqSMB2QQH5XtYVC4JMQX4QEJwg+H2TwgUKqQXk=; b=whVOd1nSbc2PjRRSDw35KUuwIGluHh9rjz72aBPRBHWv4n/OAwMabR6ZOUAacAr1k/ jzKPZkzM3WE80iLOtVPEGJQhnL8z0s0d5HlOUuTmppy6PvYZWVJ/a9ftDlJWrou/NoIi 4i/6mpDIfrvYZDmK229Aa/xqa09LILEJr97AUpH/CjFPhV5sAIOdASFEKCTMkqSWkJYy u+6Z2OmQ7VKF2Zu1z+Uxm585YY0T9p3LH0dwBt+h0ljzp7DM/RamAmfCUPeTO0o/XTC5 bNAHNQZd5DRXPudJV2ke+spWsEVybQ5yaWNEJ3KcEjRWRSi3WA8k2vAXGZ4W0T6t9DnF mAJQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=rothenpieler.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id by25si7825393ejb.281.2020.08.04.08.40.04; Tue, 04 Aug 2020 08:40:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=rothenpieler.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725932AbgHDPjr (ORCPT + 99 others); Tue, 4 Aug 2020 11:39:47 -0400 Received: from btbn.de ([5.9.118.179]:35974 "EHLO btbn.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727038AbgHDPjq (ORCPT ); Tue, 4 Aug 2020 11:39:46 -0400 Received: from [IPv6:2001:16b8:64d7:4500:fc3b:cfd2:151e:7636] (200116b864d74500fc3bcfd2151e7636.dip.versatel-1u1.de [IPv6:2001:16b8:64d7:4500:fc3b:cfd2:151e:7636]) by btbn.de (Postfix) with ESMTPSA id 5D5604DDC2; Tue, 4 Aug 2020 17:39:40 +0200 (CEST) Subject: Re: NFS over RDMA issues on Linux 5.4 To: Chuck Lever , Leon Romanovsky Cc: Linux NFS Mailing List , linux-rdma References: <8a1087d3-9add-dfe1-da0c-edab74fcca51@rothenpieler.org> <20200804093635.GA4432@unreal> <92a5a932-b843-eed3-555e-7557ccc1f308@rothenpieler.org> <20200804122557.GB4432@unreal> <20200804134642.GC4432@unreal> <45BA86D8-52A3-407E-83BE-27343C0182C5@oracle.com> From: Timo Rothenpieler Message-ID: <7c7418cb-7f7a-5de3-2025-7bde5cd5ac2a@rothenpieler.org> Date: Tue, 4 Aug 2020 17:39:40 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org 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?).