From owner-freebsd-fs@FreeBSD.ORG Wed Dec 31 19:13:53 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E57B7106564A for ; Wed, 31 Dec 2008 19:13:53 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from aeryn.cs.uoguelph.ca (aeryn.cs.uoguelph.ca [131.104.20.160]) by mx1.freebsd.org (Postfix) with ESMTP id A47128FC1B for ; Wed, 31 Dec 2008 19:13:53 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by aeryn.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id mBVJDqDh002301; Wed, 31 Dec 2008 14:13:52 -0500 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id mBVJGAs20550; Wed, 31 Dec 2008 14:16:10 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 31 Dec 2008 14:16:10 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Bryan Alves In-Reply-To: <92f477740812301246k7ed77511oc969c22a3b5aad4d@mail.gmail.com> Message-ID: References: <92f477740812291739o7c0b840bsd1cce4375577c41f@mail.gmail.com> <92f477740812301246k7ed77511oc969c22a3b5aad4d@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.20.161 Cc: freebsd-fs@freebsd.org Subject: Re: NFS locking problems with 7.0-RELEASE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2008 19:13:54 -0000 On Tue, 30 Dec 2008, Bryan Alves wrote: >> - Download my server patches (ftp.cis.uoguelph.ca/pub/nfsv4/FreeBSD7) and >> switch to using nfsv4, which has integral locking in the protocol. >> >> Have a good holiday, rick >> >> > Is there another location where I can get the nfs4 patches? That FTP seems > to be down. > Seems to be working here. Just "ftp ftp.cis.uoguelph.ca", login "anonymous", then "cd pub/nfsv4/FreeBSD7". (Is it that you can't find the machine? It's IP# is 131.104.48.112.) > Also, outside the scope of this list, but since the discussion is opened, I > might as well ask: > > If this NFS is the only remote mount that involves writing (it's opened > read-only in other locations), and it's read/write locally, is it safe to > use local locking? > Yes, I believe so. Even if there are multiple clients rw mounting a file system, local locking should be fine unless there are multiple clients writing the same file in the file system. (With a single writer and multiple readers, an application might run into coherency problems if that application was written to use byte range locking to maintain coherency (ie. most recently written data visible to the readers), but that seems unlikely to matter for most applications/environments. (And I'm not sure if the NLM is wired into NFS is such a way as to maintain full coherency for the locked byte ranges anyhow, since normally NFS does not maintain full coherency?) Have a happy new years, rick