From owner-freebsd-stable@FreeBSD.ORG Mon May 15 03:57:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CFC716A400 for ; Mon, 15 May 2006 03:57:15 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from misav02.sasknet.sk.ca (misav07.sasknet.sk.ca [142.165.20.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF2B543D49 for ; Mon, 15 May 2006 03:57:14 +0000 (GMT) (envelope-from shurd@sasktel.net) Received: from bgmpomr2.sasknet.sk.ca ([142.165.72.23]) by misav07 with InterScan Messaging Security Suite; Sun, 14 May 2006 21:57:13 -0600 Received: from [192.168.0.193] ([142.165.59.202]) by bgmpomr2.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0IZA00AHUGBDQG10@bgmpomr2.sasknet.sk.ca> for freebsd-stable@freebsd.org; Sun, 14 May 2006 21:57:13 -0600 (CST) Date: Sun, 14 May 2006 21:57:12 -0600 From: Stephen Hurd In-reply-to: <018801c677cb$7f574510$071872cf@Leadmon.local> To: Howard Leadmon Message-id: <4467FC18.1090607@sasktel.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT References: <018801c677cb$7f574510$071872cf@Leadmon.local> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.0.1) Gecko/20060413 SeaMonkey/1.0 Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 03:57:15 -0000 Howard Leadmon wrote: > Would this just be lockd, or should I disable both lockd and statd? I notice > in the rc.conf it claims they are both supposed to be enabled, so not sure > what issues I run into if I disable them, if any. > No need to disable rpc.statd though I don't know if any other programs request monitoring. The issues you'll run into is simply a lack of any locks on the mounted drive. This can easily lead to file corruption if multiple programs or multiple instances of a single program change the same file at the same time. Many programs will use NFS-safe lockfiles if configure to do so, which is often a useable workaround in a lockd-free world. If you're only using the files read-only, or only a single process uses files on the mount at a time (on *all* systems) then there's no issue at all.