From owner-freebsd-current@FreeBSD.ORG Fri Jul 3 19:39:42 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67F79106566C for ; Fri, 3 Jul 2009 19:39:42 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1913F8FC16 for ; Fri, 3 Jul 2009 19:39:41 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAKv7TUqDaFvI/2dsb2JhbADNYIQSBYE6 X-IronPort-AV: E=Sophos;i="4.42,344,1243828800"; d="scan'208";a="40153151" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 03 Jul 2009 15:39:41 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 2BE5194009E; Fri, 3 Jul 2009 15:39:41 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bzGyydD+rX4s; Fri, 3 Jul 2009 15:39:40 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 432F0940062; Fri, 3 Jul 2009 15:39:40 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n63Jg5u18625; Fri, 3 Jul 2009 15:42:05 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 3 Jul 2009 15:42:05 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Jilles Tjoelker In-Reply-To: <20090702212505.GA39889@stack.nl> Message-ID: References: <20090702121640.D245@maildrop.int.zabbadoz.net> <20090702122955.J245@maildrop.int.zabbadoz.net> <20090702212505.GA39889@stack.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Bjoern A. Zeeb" , FreeBSD current mailing list Subject: Re: Install from NFS onto NFS fails on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 19:39:42 -0000 On Thu, 2 Jul 2009, Jilles Tjoelker wrote: > > This could be because of NFS "sillyrename". To avoid some ESTALE errors, > the NFS client (for NFSv2 and NFSv3 at least) renames if you delete a > file that is currently in use (in this case, the rm binary). Because the > renamed file (name typically starts with .nfs) is in the same directory, > this causes problems when removing directories. Once the file is no > longer in use, it is finally deleted. > Yes, if some file that was in that directory is still open (or mmap'd and the process hasn't yet exit()'d), it will exist as a file named ".nfsXXX" until the v_usecount goes to 0 and then it's removed, which would explain it. > Maybe NFSv4 has a cleaner way to keep a file with 0 links as long as it > is open. > Afraid not. NFSv4 has an Open, but it is an open share lock and not a POSIX style open, so NFSv4 clients still do the silly rename. (ie. The NFSv4 Remove Op is defined as removing the file and not just unlinking it and the NFSv4 server isn't required to retain the file after removal if it is Open'd by a client.) rick