Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp4586151pxb; Mon, 27 Sep 2021 22:18:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxsqJafZnoPe5tBu8p9HTSW+nj1bXR1vbSd5dqPGbjv3oM5BLdAmVREdrk/qXEtnDEPnJ5l X-Received: by 2002:a17:90b:3291:: with SMTP id ks17mr3214668pjb.97.1632806293320; Mon, 27 Sep 2021 22:18:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632806293; cv=none; d=google.com; s=arc-20160816; b=rzm1nMYW5iEcbG99CPOCNVwxGvwoLa/ZtTzEB+kqgfyjISFXwaSeSqNMPPzlmLXydi 46Vgxavgeh6Gb8Mr4occ0JXL+jF1M81uvBcYDPpogsjpfBtdDYf4SjE7SNdJHY8n81Cd sImo9k5RI79qap9KhuUVhV39FAYqleJAqxhk/go3XO7zcZmaM4mEhGo/thwFYJaBMokK xMKY8LGkd9GfBNGaEl56kiXz9hQqZn3JC5aKGaHYIsTp8fr31AvnzTQpgyzr5N81rCCL tRQRo9LtaOM96WGsURoiIAvdMjWqfBRUdqOR/mXusJbwZqi81VLTNwGrwlSNzs9U/Gnz VuKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:message-id:user-agent :references:in-reply-to:subject:cc:to:from:date:mime-version; bh=OiVcXBJ0k3+auaXGAeR47nORGlUAym/xmVAzxfWnfeU=; b=L+F11CpN/7EoOw36cBre/JWJKi9/GWNlEDNpwkIrnZhBjXkAtIbMA850LZbkden4Rp GfJVnvvFvi+F+eaZGpQPb+LLmP/22YGb4avOYqoMbRb3SqJIfaC0oFf+1Gdft3vwAlNt 3MaZXjJiAoUUL2lOC4wtxgAq0XeiYP0kdwq9uQ7r0ryRBq4/iK0wKxwJOdo9fQ6ZUUsJ RsXjkxsB0CYuttBgqwWEdb4YsJ7QomSDUjncbIwSbxh5Km326K2dmzv9ZFCaTGNf/Yb6 8s01STyXPa0gZZwH7NHm4jr/tOMHqCEGkDsM5h6nJVqDVprJCAaRvdWCbuO5QKGjvav/ bBlw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d12si5877233pln.97.2021.09.27.22.17.43; Mon, 27 Sep 2021 22:18:13 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234094AbhI1FTU (ORCPT + 99 others); Tue, 28 Sep 2021 01:19:20 -0400 Received: from virgo01.ee.ethz.ch ([129.132.2.226]:59152 "EHLO virgo01.ee.ethz.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233681AbhI1FTT (ORCPT ); Tue, 28 Sep 2021 01:19:19 -0400 X-Greylist: delayed 356 seconds by postgrey-1.27 at vger.kernel.org; Tue, 28 Sep 2021 01:19:19 EDT Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 4HJSKW2qg6zMl4h; Tue, 28 Sep 2021 07:11:43 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2XxBrQzb18-a; Tue, 28 Sep 2021 07:11:41 +0200 (CEST) X-MtScore: NO score=0 Received: from email.ee.ethz.ch (webbi10.ee.ethz.ch [129.132.52.168]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Tue, 28 Sep 2021 07:11:41 +0200 (CEST) MIME-Version: 1.0 Date: Tue, 28 Sep 2021 07:11:41 +0200 From: Salvatore Bonaccorso To: "J. Bruce Fields" Cc: linux-nfs@vger.kernel.org, Chuck Lever Subject: Re: nfsd4_process_open2 failed to open newly-created file! status=10008 ; warning at fs/nfsd/nfs4proc.c for nfsd4_open In-Reply-To: <20210927155338.GA30593@fieldses.org> References: <20210927061025.GA20892@varda.ee.ethz.ch> <20210927155338.GA30593@fieldses.org> User-Agent: Roundcube Webmail/1.4.11 Message-ID: X-Sender: bonaccos@ee.ethz.ch Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Hi Bruce, On 27.09.2021 17:53, J. Bruce Fields wrote: > On Mon, Sep 27, 2021 at 08:10:31AM +0200, Salvatore Bonaccorso wrote: >> We recently got the following traces on a NFS server, but I'm not sure >> how to further debug this, any hints? > > The server creates and opens a file in two steps, though it should > really be a single atomic operation. > > That means there's a small possibility somebody could intervene and do > something like change the permissions: > >> >> [5746893.904448] ------------[ cut here ]------------ >> [5746893.910050] nfsd4_process_open2 failed to open newly-created >> file! status=10008 > > 10008 is NFS4ERR_DELAY, so maybe somebody managed to get a delegation > before we finished opening? > > We should be able to prevent that.... > > In your setup are there processes quickly opening new files created by > others? This is very possible. The NFS server is used as a "scratch" place accessible from compute cluster where people can have multiple jobs simultaneously running through Slurm and accessing the data. So it is possible that user create new files from one running instance and accessing it quickly from the other nodes. I'm so far was unable to arificially trigger the issue but is there anything I can try out to get more information useful for you? Regards, Salvatore