From owner-freebsd-fs@freebsd.org Mon Dec 12 16:41:20 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EA61C73051 for ; Mon, 12 Dec 2016 16:41:20 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D41A68DE for ; Mon, 12 Dec 2016 16:41:19 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190e-efbff70000000b7b-6e-584ed1f88394 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 03.35.02939.8F1DE485; Mon, 12 Dec 2016 11:36:08 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id uBCGa7on013484; Mon, 12 Dec 2016 11:36:08 -0500 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id uBCGa47M001725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Dec 2016 11:36:07 -0500 Date: Mon, 12 Dec 2016 10:36:04 -0600 From: Benjamin Kaduk To: Colin Percival Cc: "freebsd-fs@freebsd.org" Subject: Re: ESTALE after cwd deleted by same NFS client Message-ID: <20161212163603.GV8460@kduck.kaduk.org> References: <01000158f023675b-41b35a73-4428-4937-853b-62db4fb9b984-000000@email.amazonses.com> <20161212054233.GU8460@kduck.kaduk.org> <01000158f1abc081-d4eddc58-3b4b-41dd-aa1e-0157d2fad812-000000@email.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01000158f1abc081-d4eddc58-3b4b-41dd-aa1e-0157d2fad812-000000@email.amazonses.com> User-Agent: Mutt/1.6.1 (2016-04-27) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixCmqrPvjol+EweMWWYujHasYLY49/snm wOQx49N8Fo/5z08yBzBFcdmkpOZklqUW6dslcGV0Pa0sWMxRMe3RR9YGxj1sXYycHBICJhIn 1ywGsrk4hATamCT+7HrLBOFsZJQ4dXwrI0iVkMBVJomDC3JBbBYBVYmHd26DxdkEVCQaui8z g9giApoSByevBJvKLGAqsbn/NhOILSxgIfGrfztYDa+AscSX6RMYIRbcZZR4s20BO0RCUOLk zCcsEM1aEjf+vQRq5gCypSWW/+MACXMKxEu8ePcHbK+ogLJEw4wHzBMYBWYh6Z6FpHsWQvcC RuZVjLIpuVW6uYmZOcWpybrFyYl5ealFusZ6uZkleqkppZsYwUEqybeDcVKD9yFGAQ5GJR5e gU1+EUKsiWXFlbmHGCU5mJREeW0uAIX4kvJTKjMSizPii0pzUosPMUpwMCuJ8IYBY0OINyWx siq1KB8mJc3BoiTOeynTPUJIID2xJDU7NbUgtQgmK8PBoSTBaw7SKFiUmp5akZaZU4KQZuLg BBnOAzRcD2Qxb3FBYm5xZjpE/hSjopQ4bzxIswBIIqM0D64XlEQksvfXvGIUB3pFmNcUpIoH mIDgul8BDWYCGvx8nzfI4JJEhJRUA6PChCC7H8scrVqmJoVqzMn6/faw8gOVvnUrdp2yaPHY Pn9vTpGmVbTdEsHTV+ZNEFRe5NGpouxpFhjj/f/l/7l7XLcsXrzQrXQ+G9N+W99NyTUnkirj 5upz+ditjCySkHc9M0d/e6jSjNKv1wPSN/xJieS4fsXI5X3XWvVtUZedam925DSwH1ViKc5I NNRiLipOBADnGAsB/QIAAA== X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 16:41:20 -0000 On Mon, Dec 12, 2016 at 06:15:14AM +0000, Colin Percival wrote: > On 12/11/16 21:42, Benjamin Kaduk wrote: > > On Sun, Dec 11, 2016 at 11:06:42PM +0000, Colin Percival wrote: > >> If I run the following with /nfs/ being an NFS mount: > >> # mkdir /nfs/foo > >> # touch /nfs/foo/bar > >> # cd /nfs/foo > >> # rm -r /nfs/foo > >> # rm bar > >> > >> Then the final 'rm bar' fails with 'Stale NFS file handle'. > > > > Amusingly, this just came up recently: > > > > https://www.ietf.org/mail-archive/web/nfsv4/current/msg15115.html (et seq) > > > > But I guess you did not specify which version of the NFS protocol you were > > using... > > I'm using NFSv4.1, but this isn't quite the same... that link refers to having > one NFS client remove a file out from underneath a different client, while I'm > talking about having an NFS client remove a file from underneath *itself*. I thought the reply mentioned (in passing) the case of a client removing a file out from under itself as well. But, maybe I was reading too fast. -Ben