Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp174161pxa; Tue, 4 Aug 2020 02:39:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwUkUeBg4ezK/Adq5OOkBYS7cFDbDvO/rwPgE+AqDNluG3YplT3L8l0i7ld5JaLklXUOU8C X-Received: by 2002:aa7:dd15:: with SMTP id i21mr19757305edv.153.1596533967571; Tue, 04 Aug 2020 02:39:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596533967; cv=none; d=google.com; s=arc-20160816; b=ZBEiti4MYDRnFt9nBMdZs7gAOdUZQma8H5ezUvdV/iWrS8RsOXlIKc6KW6Z8aAqjH7 9Hz9j4Ybok11zgSEpInwuuYjb1LrEhg6Zavf0ZiENMkKqGVtn+TdhCotVYIsx0ZNbLlw NHHlDAhdwFfkYmm5rIYGVlihly/YDb5UrDEl6LErO2mEM07ZSIBvVej2i7BXsTEbnTjc te1IxGxcijYsGkmP/JYApzRIpnuC2gzldWP0fTlr4UiuKi+vaaK1Be7EI3VN2o202alb E00wdJZQsL65+wSFW0U1zsnWBJ+qql+bzrTxVbVygqbWtbHjcYMJpGBp2sHuyHeplZlM C+Rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=tLkmAKfM39iELVhtLgdrORtpCbCIiL/zT4iG08JlLu0=; b=D2blugofi6JXeoXkX1WsSI2XoNAdRPCePuUXvmIPBZx3YlTodre52hCoQ9stgQr0OP naXTsmUvcRAkJFim1rLJRVPRnPoe+OdywLHfxY5Yy47HbHcLpBzgHQOlQdLZZO3ZEQWn /9/QWuKOIpZG5TgyCTa8Su6YhefXCq1LC79VgnUXoVfNNqj6Basav9G1la/6RMMW9nmT LYJK2JddVoN2XsrQSzF5Zh5ZhiYYv20eH7ISwhdzs6vTyA/R8Y+WEGiY2cOE8yJq4kbw luIFXarwNB66OXvmVxuYVN0qMhlVxvDC5PMqJH0h7M3q/J/hteMSXwGQZEs/wD/XoN2z S+nw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=W2naIBEY; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c7si12112704edw.303.2020.08.04.02.38.54; Tue, 04 Aug 2020 02:39:27 -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; dkim=pass header.i=@kernel.org header.s=default header.b=W2naIBEY; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727997AbgHDJgn (ORCPT + 99 others); Tue, 4 Aug 2020 05:36:43 -0400 Received: from mail.kernel.org ([198.145.29.99]:40534 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726339AbgHDJgm (ORCPT ); Tue, 4 Aug 2020 05:36:42 -0400 Received: from localhost (unknown [213.57.247.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 45B0922B45; Tue, 4 Aug 2020 09:36:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596533802; bh=tLkmAKfM39iELVhtLgdrORtpCbCIiL/zT4iG08JlLu0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=W2naIBEYV2FDAqu+ODACQkrhSFTQCOnbX1zyWdOdDTQGg1B+QtC8ygnY+PRTehjDQ RGiSVr6fFwuWzSDQCqpfG5uiSTS3QONGqPVzjqEu4EgiUyDv3W7jFDrK/VyX6UvLWe BRzV1cnwyDleLEVkp3pnS3VJQaQT8z9Rxz05Vf3M= Date: Tue, 4 Aug 2020 12:36:35 +0300 From: Leon Romanovsky To: Chuck Lever Cc: Timo Rothenpieler , Linux NFS Mailing List , linux-rdma Subject: Re: NFS over RDMA issues on Linux 5.4 Message-ID: <20200804093635.GA4432@unreal> References: <8a1087d3-9add-dfe1-da0c-edab74fcca51@rothenpieler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Mon, Aug 03, 2020 at 12:24:21PM -0400, Chuck Lever wrote: > Hi Timo- > > > On Aug 3, 2020, at 11:05 AM, Timo Rothenpieler wrote: > > > > Hello, > > > > I have just deployed a new system with Mellanox ConnectX-4 VPI EDR IB cards and wanted to setup NFS over RDMA on it. > > > > However, while mounting the FS over RDMA works fine, actually using it results in the following messages absolutely hammering dmesg on both client and server: > > > >> https://gist.github.com/BtbN/9582e597b6581f552fa15982b0285b80#file-server-log > > > > The spam only stops once I forcibly reboot the client. The filesystem gets nowhere during all this. The retrans counter in nfsstat just keeps going up, nothing actually gets done. > > > > This is on Linux 5.4.54, using nfs-utils 2.4.3. > > The mlx5 driver had enhanced-mode disabled in order to enable IPoIB connected mode with an MTU of 65520. > > > > Normal NFS 4.2 over tcp works perfectly fine on this setup, it's only when I mount via rdma that things go wrong. > > > > Is this an issue on my end, or did I run into a bug somewhere here? > > Any pointers, patches and solutions to test are welcome. > > I haven't seen that failure mode here, so best I can recommend is > keep investigating. I've copied linux-rdma in case they have any > advice. The mentioning of IPoIB is a slightly confusing in the context of NFS-over-RDMA. Are you running NFS over IPoIB? From brief look on CQE error syndrome (local length error), the client sends wrong WQE. Thanks > > -- > Chuck Lever > > >