From owner-freebsd-fs@FreeBSD.ORG Wed Dec 24 23:15:06 2014 Return-Path: Delivered-To: freebsd-fs@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 61EA8D1E for ; Wed, 24 Dec 2014 23:15:06 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 265FE313B for ; Wed, 24 Dec 2014 23:15:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtkEAExIm1SDaFve/2dsb2JhbABcg1hYBIMAw1SFcYEoAQEBAQF9hDaBCwINGQJfE4gsDaROj0SVSwEBAQEGAQEBAQEBGASBIY4dgyOBQQWJS4gJhkGNCoM5IoQMIDEBgUR+AQEB X-IronPort-AV: E=Sophos;i="5.07,639,1413259200"; d="scan'208";a="180869386" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 24 Dec 2014 18:14:59 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 89FC1E7956 for ; Wed, 24 Dec 2014 18:14:58 -0500 (EST) Date: Wed, 24 Dec 2014 18:14:58 -0500 (EST) From: Rick Macklem To: FreeBSD Filesystems Message-ID: <962761800.2101281.1419462898537.JavaMail.root@uoguelph.ca> Subject: RFC: new NFS mount option to work around Solaris server bug MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Dec 2014 23:15:06 -0000 Hi, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193128 This bug report discusses a bug in the Solaris NFS server that is tickled by the way FreeBSD currently does exclusive open in the NFS client. FreeBSD sets both the mtime to the time of the client and also the file's mode using a Setattr RPC done after an exclusive create of the file in an exclusive open. Jason (jnaughto@ee.ryerson.ca) was able to figure out that the server bug can be avoided if the mtime is set to the server's time (xxx_TOSERVER option in the Setattr RPC request). I'd like to propose a new mount option that forces the FreeBSD client to use xxx_TOSERVER for setting times, mostly to be used as a work around for this Solaris server bug. 1 - Does doing this make sense to others? 2 - If the answer to one is "Yes", then what do you think the option should be called? useservertime useservtm ust OR ?? Thanks in advance for your comments, rick