From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 20:07:13 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 2DD8416A47C for ; Sun, 2 Jul 2006 20:07:13 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B17DF43DA8 for ; Sun, 2 Jul 2006 19:34:10 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 25CE32919EF; Sun, 2 Jul 2006 16:34:07 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 10301-07; Sun, 2 Jul 2006 19:34:10 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 0BE6E290C6D; Sun, 2 Jul 2006 16:34:06 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 0CA404853F; Sun, 2 Jul 2006 16:34:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 05B5233DF1; Sun, 2 Jul 2006 16:34:10 -0300 (ADT) Date: Sun, 2 Jul 2006 16:34:09 -0300 (ADT) From: User Freebsd To: Francisco Reyes In-Reply-To: Message-ID: <20060702162942.D1103@ganymede.hub.org> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 20:07:13 -0000 On Sat, 1 Jul 2006, Francisco Reyes wrote: > 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.. Since there are several of us experiencing what looks to be the same sort of deadlock issue, I beseech you not to give up ... right now, all we've been able to get to the developers is virtually useless information (vmstat and such shows the problem, but it doesn't allow developers to identify the problem) ... Is this a problem that you can easily recreate, even on a non-production machine? In my case, I have one machine fully configured for debugging, but, of course, since re-configuring it, it hasn't exhibited the problem ... if most of us get our machines configured properly to give useful information to the developers to debug this, the faster it will get fixed ... My experience with most of the developers is that if you can get into DDB and give them 'internal traces' of the code, bugs tend to get fixed very quickly ... vmstat/ps give "external views", more summaries then anything ... its the details "under the hood" that they need ... its not much different then your auto-mechanic ... try telling him there is a 'knocking under the hood, please tell me how to fix it, but you can't have my car', and he'll brush you off ... give him 30 minutes under the hood, and not only will he have identified it, but he'll probably fix it too ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664