From owner-freebsd-fs@FreeBSD.ORG Thu Sep 17 14:58:29 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 7C27B106580F for ; Thu, 17 Sep 2009 14:58:29 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2B2188FC0C for ; Thu, 17 Sep 2009 14:58:28 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAM7rsUqDaFvJ/2dsb2JhbADfa4QYBQ X-IronPort-AV: E=Sophos;i="4.44,404,1249272000"; d="scan'208";a="48376373" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 17 Sep 2009 10:58:28 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 3ACC2FB80D6; Thu, 17 Sep 2009 10:58:28 -0400 (EDT) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2H-RHJ7nVgr; Thu, 17 Sep 2009 10:58:27 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 29FC2FB80A1; Thu, 17 Sep 2009 10:58:27 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8HF3t203162; Thu, 17 Sep 2009 11:03:55 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Thu, 17 Sep 2009 11:03:55 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: =?utf-8?B?R2Vycml0IEvDvGhu?= In-Reply-To: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> Message-ID: References: <20090917094412.962e8729.gerrit@pmp.uni-hannover.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-1253199835=:1169" 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: Thu, 17 Sep 2009 14:58:29 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-851401618-1253199835=:1169 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 17 Sep 2009, Gerrit K=C3=BChn wrote: > > I upgraded a FreeBSD fileserver last week from 7.0-stable to 7.2-stable > and experience some weird problems now with Linux NFS clients. > The Linux Clients mount their home directories via nfs. I usually use > "nolock" on the client side, because file locking was always troublesome > in the past. On the Clients the users run kde 3.5 or 4.2. > After the update of the server kde 3.5 quit starting up (after logging > in with kdm) on the spalsh screen and comes up with some kind of I/O erro= r > when writing to the home dir. At the same time the server complains about > > kernel: NLM: failed to contact remote rpcbind, stat =3D 5, port =3D 28416 > I think this happens when the nlm in the server tries to contact the client. I believe setting the following in the server's /etc/rc.conf and rebooting the server (or just killing off lockd on the server), combined with "nolock" as you have on the above Linux mount, might work ok: =09rpc_lockd_enable=3D"NO" =09rpc_statd_enable=3D"NO" Imo, the nlm protocol was poorly designed and has always resulted in interoperability problems. Although I fiddle with NFS, I avoid the NLM like the plague:-) Good luck with it, rick ps: If you need to run the lockd on the server, starting the lockd in the Linux client might help, although I'd still use "nolock" on the Linux mount. ---559023410-851401618-1253199835=:1169--