From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 44E7AC433F5 for ; Fri, 24 Sep 2021 19:03:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 212C5610CB for ; Fri, 24 Sep 2021 19:03:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346095AbhIXTF1 (ORCPT ); Fri, 24 Sep 2021 15:05:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45930 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229930AbhIXTF0 (ORCPT ); Fri, 24 Sep 2021 15:05:26 -0400 Received: from fieldses.org (fieldses.org [IPv6:2600:3c00:e000:2f7::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 443E8C061571 for ; Fri, 24 Sep 2021 12:03:53 -0700 (PDT) Received: by fieldses.org (Postfix, from userid 2815) id 359BF6814; Fri, 24 Sep 2021 15:03:52 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org 359BF6814 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org; s=default; t=1632510232; bh=jiFlW5P4EJb78zkwd+/lDROWq7Wav9LBFK4/hyCNR2M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=U9QLfC4SES3wJ6iDLfomIzKECxBEmhm8woNYUSIxTUOR59hNujwvsRS9iFmOvQCX3 MdYz3EI1cYyK+ZubYj8mxlioDZj/tXxwTGkIk1c38hRKYB+FvVuGjG2lJual0Ph5Pp Cz82c+lE49mR2gS4FNvZIavejUMOgiImLiuelAb0= Date: Fri, 24 Sep 2021 15:03:52 -0400 From: "J. Bruce Fields" To: Kazi Anwar Cc: linux-nfs@vger.kernel.org Subject: Re: nfs4err_delay Message-ID: <20210924190352.GD13115@fieldses.org> References: <20210924163948.GB13115@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Fri, Sep 24, 2021 at 12:54:30PM -0500, Kazi Anwar wrote: > Yes, both clients and server are centos 7.6. And the NFS4ERR_DELAY is > a response to a REMOVE. > I will need to check on the locks the next time it happens. Can you > share what you are thinking? Offhand the only reason I can think a server would return DELAY is that there's a delegation on the file being removed, and the delegation recall and return isn't working for some reason. If that's the case, it should succeed after about 90 seconds. Also, you can workaround the problem by turning of delegations and leases with "echo 0 >/proc/sys/fs/leases_enable". --b. > > thanks, > Kazi > > On Fri, Sep 24, 2021 at 11:39 AM J. Bruce Fields wrote: > > > > On Wed, Sep 22, 2021 at 03:56:23PM -0500, Kazi Anwar wrote: > > > We are running nfs v 4.1 on centos 7.6. > > > We are seeing an NFS issue where when files/dirs are deleted from a > > > client they are occasionally stuck at unlinkat system call(according > > > to strace its stuck for 100.5 secs every time). Can anyone explain > > > this behavior? > > > Running tcp dump shows nfs4err_delay status sent from the server to > > > the stuck client. > > > > Client and server are both centos 7.6? > > > > Is the NFS4ERR_DELAY a reponse to a REMOVE? > > > > Does /proc/locks show a delegation held on the file the client's trying > > to remove? > > > > --b.