From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 06:39:51 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 9665516A407 for ; Sun, 2 Jul 2006 06:39:51 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B36243D48 for ; Sun, 2 Jul 2006 06:39:50 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FwvcP-0009Td-Ls; Sun, 02 Jul 2006 09:39:45 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Francisco Reyes In-reply-to: References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> Comments: In-reply-to Francisco Reyes message dated "Sat, 01 Jul 2006 21:13:26 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jul 2006 09:39:45 +0300 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue 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: Sun, 02 Jul 2006 06:39:51 -0000 > John Hay writes: > > > I only started to see the lockd problems when upgrading the server side > > to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x > > and 7-current and the lockd problem only showed up when upgrading the > > server from 5.x to 6.x. > > It confirms the same we are experiencing.. constant freezing/locking issues. > I guess no more 6.X for us.. for the foreseable future.. just to add some more 'ingredients' to the problems: 1- we are suffering from the lockd syndrome 2- am-utils sometimes failes - specially /net (type:=host) [there seems to be a race condition] both problems are new since 6.1 and now, on a 'mostly idle' machine, after failing to compile openoffice-2.0 the lockd is 'spinning' with no real work, at least so it seems: last pid: 69935; load averages: 0.16, 0.10, 0.08 up 1+16:37:25 09:37:09 44 processes: 1 running, 43 sleeping CPU states: 2.6% user, 0.0% nice, 0.4% system, 0.4% interrupt, 96.6% idle Mem: 129M Active, 2796M Inact, 157M Wired, 106M Cache, 214M Buf, 132M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 513 root 1 96 0 48628K 45304K select 1 67:39 5.13% rpc.lockd 498 root 1 4 0 2420K 868K - 1 23:38 0.83% nfsd 419 root 1 96 0 5408K 2088K select 1 98:13 0.00% amd-6.1.5 danny