From owner-freebsd-stable@FreeBSD.ORG Mon Dec 22 10:54:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CBFBEE3 for ; Mon, 22 Dec 2014 10:54:28 +0000 (UTC) Received: from mx1.informatik.uni-stuttgart.de (mailgw.informatik.uni-stuttgart.de [129.69.211.41]) by mx1.freebsd.org (Postfix) with ESMTP id 6082A1064 for ; Mon, 22 Dec 2014 10:54:27 +0000 (UTC) Received: from azu.informatik.uni-stuttgart.de (azu.informatik.uni-stuttgart.de [129.69.218.66]) by mx1.informatik.uni-stuttgart.de (Postfix) with ESMTP id D104E60B0 for ; Mon, 22 Dec 2014 11:54:19 +0100 (CET) Received: by azu.informatik.uni-stuttgart.de (Postfix, from userid 19691) id AAE602E85; Mon, 22 Dec 2014 11:54:15 +0100 (MET) Date: Mon, 22 Dec 2014 11:53:43 +0100 (MET) From: Christian Corti To: freebsd-stable@freebsd.org Subject: Re: New bug with O_CREAT|O_EXCL and NFS? In-Reply-To: <376853369.1281572.1419028998536.JavaMail.root@uoguelph.ca> Message-ID: References: <376853369.1281572.1419028998536.JavaMail.root@uoguelph.ca> User-Agent: Alpine 2.02 (SUN 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2014 10:54:28 -0000 On Fri, 19 Dec 2014, Rick Macklem wrote: > If you are using a Solaris NFS server then, yes, it is a known bug in > the Solaris NFS server. See: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193128 Yes, indeed, I'm using a Solaris NFS server. > Until I add a mount option in the client to force "use server's time" > workarounds are: > - Use a non-Solaris NFS server. > - Use NFSv2, which seems to work ok. ("nfsv2" or "vers=2" mount option) > - Hack your kernel with the patch in the bug report. It seems that using NFSv4 solves that problem, too. That means I have to migrate from amd to autofs since amd apparently doesn't support NFSv4. Christian