From owner-freebsd-stable@FreeBSD.ORG Thu Dec 1 17:32:55 2005 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 A5E0416A41F for ; Thu, 1 Dec 2005 17:32:55 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D13B43D5E for ; Thu, 1 Dec 2005 17:32:54 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out0.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1EhsIf-0001No-Da for ; Thu, 01 Dec 2005 18:32:53 +0100 Received: (qmail 57665 invoked from network); 1 Dec 2005 17:32:52 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 1 Dec 2005 17:32:52 -0000 Date: Thu, 01 Dec 2005 18:32:50 +0100 To: freebsd-stable@freebsd.org References: <20051201164955.788ba69e.gerrit@pmp.uni-hannover.de> From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20051201164955.788ba69e.gerrit@pmp.uni-hannover.de> User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Subject: Re: nfs locking (was: Re: OOO 2.0 compiles but doesn't work properly) 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: Thu, 01 Dec 2005 17:32:55 -0000 On Thu, 01 Dec 2005 16:49:55 +0100, Gerrit Kühn wrote: > On Wed, 30 Nov 2005 10:29:02 -0500 Robert Huff wrote > about OOO 2.0 compiles but doesn't work properly: > > RH> > The home directory is coming from a nfs-server, so the user-setup > RH> > should be identical. I already tried to delete .openoffice.org2, > RH> > but that didn't help either. Any further hints? > > RH> Yes - check the archives. There was at least one other person > RH> reporting problems with OpenOffice+NFS. > > Yes, I see... the problem seems so be that you have to run lockd and > statd > to get ooo running on nfs. The machine where everything's working fine is > running 5.4 with statd and lockd. The machine with the problems is > running > 6.0 and didn't have statd and lockd activated. > However, activating them (and rebooting) didn't solve the problem here. > That's why I'm taking this over to -stable mailing list: > > I've got a FreeBSD 6.0 NFS client here, which is connected to a FreeBSD > 4.10-Server. Both sides are running statd and lockd, but processes > requesting locks (kdm in the first place after booting here) get stuck in > the state "lockd". The same setup works fine with a FreeBSD 5.4 client. > Are > there any known problems concerning nfs and 6.0, or do I miss anything > else? Another me too: freebsd 6.0-stable client and a Linux 2.6.x debian 3.1 server. All processes that try to lock a file hang in stats lockd. A workaround is using the -L option of mount_nfs. -- Ronald Klop Amsterdam, The Netherlands