From owner-freebsd-stable@FreeBSD.ORG Thu Dec 1 16:38:47 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 4750216A41F for ; Thu, 1 Dec 2005 16:38:47 +0000 (GMT) (envelope-from netzwerk@98eins.de) Received: from smtpin1.uni-greifswald.de (smtpin1.uni-greifswald.de [141.53.8.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E91343D55 for ; Thu, 1 Dec 2005 16:38:46 +0000 (GMT) (envelope-from netzwerk@98eins.de) Received: from arbeitsplatz2.funkhaus.radio98eins.de (hendrix.stud-ver.uni-greifswald.de [141.53.186.66]) by smtpin1.uni-greifswald.de (Content Technologies SMTPRS 4.3.17) with ESMTP id for ; Thu, 1 Dec 2005 17:38:44 +0100 From: Andreas Braml Organization: radio 98eins To: freebsd-stable@freebsd.org Date: Thu, 1 Dec 2005 17:38:38 +0100 User-Agent: KMail/1.8.2 References: <20051201164955.788ba69e.gerrit@pmp.uni-hannover.de> In-Reply-To: <20051201164955.788ba69e.gerrit@pmp.uni-hannover.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2968279.ChpLMn5Trf"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512011738.43761.netzwerk@98eins.de> 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 16:38:47 -0000 --nextPart2968279.ChpLMn5Trf Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Am Donnerstag, 1. Dezember 2005 16:49 schrieb Gerrit K=FChn: > 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? Here comes one of the dreaded "me too" posts. I'm having the same=20 problem, I guess: statd and lockd enabled on server and clients,=20 both 6.0-RELEASE (!). KDM starts, though, but login to KDE=20 fails, Gnome cannot start completely (panel does not show any=20 applets), OOo 2.0 freezes, when xkilled, rm -R .OpenOffice2 in=20 the user directory fails ("Directory not empty"). I know that users at my deployment had problems emtying the Trash=20 on the KDE desktop but this was right after the upgrade 5.4->6.0=20 some weeks ago. No severe problems since then, until yesterday=20 when none of the users was able to login anymore, Gnome broken=20 as well etc. Disabling rpc.lockd in rc.conf on the client side made the=20 symptoms disappear, but i fear the real problem is still there. Sorry that I can't give a better solution. Andreas =2D-=20 Andreas Braml Netzwerk f=FCr radio 98eins PGP: http://www.braml.org/radio.asc Please avoid sending me Microsoft Office (e.g. Word, PowerPoint) attachments. See http://www.fsf.org/philosophy/no-word-attachments.html --nextPart2968279.ChpLMn5Trf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDjycTqWapCA+Wal0RAoC2AJ4+AD98q0hVBAM4osrIprvhWNKMnACbBtrU IQEjCKT45n1YoSQT3aeIPtc= =3f+h -----END PGP SIGNATURE----- --nextPart2968279.ChpLMn5Trf--