From owner-freebsd-fs@FreeBSD.ORG Thu Jan 1 06:05:02 2009 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 57174106566C for ; Thu, 1 Jan 2009 06:05:02 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2465F8FC19 for ; Thu, 1 Jan 2009 06:05:01 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so3331870wag.27 for ; Wed, 31 Dec 2008 22:05:01 -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=29whILwfCdWwyozBV0CQ9xf7WaiAY2AqWoGHRQk8PU0=; b=IrOHZP4XAtEQo1UfUKncn/mR7XBe+56aK0dXjKjiB0Ofjtvcmm2b9cqtUgy8l0riDE zuecGryQSAMTUelLZrUIhi8Yox/kXCvDTRqAMZMiwqyQh7/WitvTWeRIki53O8D2Sjda 3DjdIGWNSvtYfelSLpgIBt3eZ78VO9kgrZ7Ew= 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=N+mmsDp5Zp92HywPqb+xKAXU1I35NS983Mt5oyGGJy9s7b25vAVYCbeQUdzbVVeZJu +wZmIRAOWaWmbpUvczK4bFogxLo4gq1tS6zsdZkzT6VrgugIAAFfFkmMny7De4XRxm4z f1PQFy45QiuerTTwp40y0lV+F8F/9Ks8bXOHY= Received: by 10.114.102.1 with SMTP id z1mr10948669wab.186.1230789901099; Wed, 31 Dec 2008 22:05:01 -0800 (PST) Received: by 10.114.155.13 with HTTP; Wed, 31 Dec 2008 22:05:01 -0800 (PST) Message-ID: <92f477740812312205x554f06bbj4b3f7dcdbeb052f3@mail.gmail.com> Date: Thu, 1 Jan 2009 01:05:01 -0500 From: "Bryan Alves" To: freebsd-fs@freebsd.org In-Reply-To: MIME-Version: 1.0 References: <92f477740812291739o7c0b840bsd1cce4375577c41f@mail.gmail.com> <92f477740812301246k7ed77511oc969c22a3b5aad4d@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: Thu, 01 Jan 2009 06:05:02 -0000 On Wed, Dec 31, 2008 at 2:16 PM, Rick Macklem wrote: > > > 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 > > Well, I've upgraded to 7.1-RC2, in hopes that the kernel NFSLOCKD would make things better. Instead it made things worse. Now when locking fails, the system completely freezes, forcing a hard reset. There doesn't seem to be a way to turn off the kernel option anymore either (if you don't compile it in it's loaded on demand, and if it's not available because you move it, the kernel dies). I had some success turning off PF completely in getting NFS working, but even that has stopped now. I no longer have any idea what the problem is, nor do I have any other directions to diagnose it. Having the system completely lock up now makes most debugging efforts take extra long and makes them be a waste of time. I'm just going back to samba. I'll give up 20+ MB/s of throughput to have a working network-mounted home directory.