From owner-freebsd-fs@FreeBSD.ORG Tue Dec 30 20:46:06 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 34301106566C for ; Tue, 30 Dec 2008 20:46:06 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id 035648FC16 for ; Tue, 30 Dec 2008 20:46:05 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so3035808wag.27 for ; Tue, 30 Dec 2008 12:46:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=jtDhu8DTeQuZSwCDhSHwxZY5uwBHbq2CG7Q+xqMAmX0=; b=sxMF+gcJpN/79WI6c8zB83VdbBmWNy5lWkyVtCdQtvmROgQ0CagpwIFWhxc8bQaA5X qJvz83K23D0VCz07IWvktdllB7YHtbaBXekPNDzVATx3Nf0BfHTpY6s6vL3cULJEVf2z 5RsDQ1ihpcEDpX7n2rw4m7VktlQpxT9Q36OoI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=kktyRwDj9bLrPx9bJkYao425bBY41vOzvydcXeRXHSi+9zpuyhqTBzFqwwF6JGNkw5 CqjJL3JwI2ERmIWHskI7QFo3Jep23SCKa+7CIMU/MorZ3ZM97rVdrl2IqZJGHBX9W1OO 39L4/HNQUGHVsVRlSziFcTDhYK8xgzE1Uw4L8= Received: by 10.114.103.4 with SMTP id a4mr10002065wac.91.1230669965303; Tue, 30 Dec 2008 12:46:05 -0800 (PST) Received: by 10.114.103.20 with HTTP; Tue, 30 Dec 2008 12:46:05 -0800 (PST) Message-ID: <92f477740812301246k7ed77511oc969c22a3b5aad4d@mail.gmail.com> Date: Tue, 30 Dec 2008 15:46:05 -0500 From: "Bryan Alves" To: freebsd-fs@freebsd.org In-Reply-To: MIME-Version: 1.0 References: <92f477740812291739o7c0b840bsd1cce4375577c41f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Tue, 30 Dec 2008 20:46:06 -0000 On Tue, Dec 30, 2008 at 2:00 PM, Rick Macklem wrote: > > > On Mon, 29 Dec 2008, Bryan Alves wrote: > > [stuff snipped] > >> When I export my home directory and mount it on my linux client, I run >> into >> all sorts of problems with file locking. The biggest problem is the >> inability to run firefox. When stracing an execution of firefox, >> execution >> hangs when opening it's .parentlock file for F_GETLK. I also notice >> messages in /var/log/messages on the client on occasion: >> >> I can't help w.r.t. getting the NKM to work (I've always thought that the > NLM protocol was a crock and avoided using it). But, here's a couple of > things you could try to avoid using the NLM. > > - Do the Linux mount with the "nolock" option. (If Ubuntu has a > "locallock" option, that would be even better, but I'm not sure what > options recent Linux's have for nfs mounts.) > > - 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. 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? --Bryan