From owner-freebsd-fs@FreeBSD.ORG Thu Dec 25 00:28:15 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 9478D680 for ; Thu, 25 Dec 2014 00:28:15 +0000 (UTC) Received: from mail-yk0-x236.google.com (mail-yk0-x236.google.com [IPv6:2607:f8b0:4002:c07::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EFB619B6 for ; Thu, 25 Dec 2014 00:28:15 +0000 (UTC) Received: by mail-yk0-f182.google.com with SMTP id 131so4233407ykp.13 for ; Wed, 24 Dec 2014 16:28:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m/wqQp51y5xNaTWfCzih4oqcMR74GRVWJ85SOtCEnZU=; b=W0HGHODVQuQkYGkJQXXlYsv9YuMT3G4wRMd8i/o3fadctqLPdBVHFJ6mgDVfFw8SN0 WXT3+XicqsoXFlL0BqIdf6NVUKYzJRx6VMHU2gOt1aWgMuosVOX6LW7keZkwrBNX8DY9 DT0T7tL9l0ft6VhZAvTFxVBr2xIMTD2I3wOR+1C7YJuSNlRStcMBzX558c0msW1Htrsg b5vB1IOuu01L7BdbgLJfZLW60+1Wn7ZBdtM1FizGUOwE6WKWFilGig0C7KruI0Gm8MEJ dY1BxRK6eVTKnFyo+q2Swk4HshHcatcfMz424Ybv3PyT3xwFVFR5vcIcX7fDuYcpP//i H7OA== MIME-Version: 1.0 X-Received: by 10.170.98.138 with SMTP id p132mr18818052yka.46.1419467294458; Wed, 24 Dec 2014 16:28:14 -0800 (PST) Received: by 10.170.90.131 with HTTP; Wed, 24 Dec 2014 16:28:14 -0800 (PST) In-Reply-To: <962761800.2101281.1419462898537.JavaMail.root@uoguelph.ca> References: <962761800.2101281.1419462898537.JavaMail.root@uoguelph.ca> Date: Wed, 24 Dec 2014 16:28:14 -0800 Message-ID: Subject: Re: RFC: new NFS mount option to work around Solaris server bug From: Mehmet Erol Sanliturk To: Rick Macklem Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Filesystems 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: Thu, 25 Dec 2014 00:28:15 -0000 On Wed, Dec 24, 2014 at 3:14 PM, Rick Macklem wrote: > 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 > Actually , this parameter should be defined ALSO in NFS server in rc.conf definition , because , to the NFS server , many different client operating systems may be connected . Setting a parameter in only FreeBSD clients will not solve COMMON time usage problem , because any change in FreeBSD client will not be available in other operating system client definitions . In that way , NFS server will set the file time irrespective of client time . If this causes an inconvenience in other operating system clients , they may use an NTP server defined in the NFS server but , unfortunately , it seems that a FreeBSD server is NOT able to be used as an NTP server with respect to FreeBSD Handbook 29.11. Clock Synchronization with NTP where it seems that ntpd is only a CLIENT to an external NTP server . At this point , it seems that there is a necessity to enable FreeBSD to define an NTP server by itself like an NFS server . Thank you very much . Mehmet Erol Sanliturk