From owner-freebsd-fs@FreeBSD.ORG Fri Oct 2 13:47:33 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 A80B71065670 for ; Fri, 2 Oct 2009 13:47:33 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 335C58FC16 for ; Fri, 2 Oct 2009 13:47:32 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id n92DlTn6007474; Fri, 2 Oct 2009 15:47:31 +0200 Received: from pmp.uni-hannover.de (theq.pmp.uni-hannover.de [130.75.117.4]) by www.pmp.uni-hannover.de (Postfix) with SMTP id D790B24; Fri, 2 Oct 2009 15:47:29 +0200 (CEST) Date: Fri, 2 Oct 2009 15:47:29 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Rick Macklem Message-Id: <20091002154729.06fbcefc.gerrit@pmp.uni-hannover.de> In-Reply-To: References: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> <20090918091435.465bfc1e.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.10.2.133625 Cc: freebsd-fs@freebsd.org Subject: Re: Fw: Linux/KDE and NFS locking on 7-stable 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: Fri, 02 Oct 2009 13:47:33 -0000 On Fri, 18 Sep 2009 10:56:59 -0400 (EDT) Rick Macklem wrote about Re: Fw: Linux/KDE and NFS locking on 7-stable: First of all, thanks to Rick for his explatations. RM> > RM> I believe setting the following in the server's /etc/rc.conf RM> > RM> and rebooting the server (or just killing off lockd on the RM> > RM> server), combined with "nolock" as you have on the above Linux RM> > RM> mount, might work ok: RM> > RM> rpc_lockd_enable="NO" RM> > RM> rpc_statd_enable="NO" RM> > RM> > I did not try that so far, as there are some clients which seem to RM> > work fine with locking. Well, in the meantime I tried more or less each and every combination of client and server setting I could think of. My first result is that locking almost every time causes troubles, because is does not work over NAT. However, even putting the server in the same subnet and using it without NAT did not make everything work with locking. Right now it looks like after booting the client KDE logins *never* work (all other nfs stuff is fine, though). After a failed login, I can umount and remount the home dir and try to login again. After doing so for some time, it suddenly works (and continues to work) obviously regardless of mount options being changed. Turning off lockd and statd on the server side does not influence this behaviour. Does anyone here have an idea how I can get a working client from the beginning on? Also, I do not even know if this is some kind of kde problem or rather a nfs problem. After all, it is rather annoying do have to login and umount/remount several times before everything works. :-) cu Gerrit