From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 12:34:37 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 AE1C716A47E for ; Mon, 3 Jul 2006 12:34:37 +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 1040343D48 for ; Mon, 3 Jul 2006 12:34:37 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 54235290C2B; Mon, 3 Jul 2006 09:34:31 -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 95263-08; Mon, 3 Jul 2006 12:34:36 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id CFF2C290C1F; Mon, 3 Jul 2006 09:34:30 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 333FF3769F; Mon, 3 Jul 2006 09:34:40 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 15CDC33DF1; Mon, 3 Jul 2006 09:34:40 -0300 (ADT) Date: Mon, 3 Jul 2006 09:34:39 -0300 (ADT) From: User Freebsd To: Francisco Reyes In-Reply-To: Message-ID: <20060703093332.D1103@ganymede.hub.org> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , freebsd-stable@freebsd.org 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: Mon, 03 Jul 2006 12:34:37 -0000 On Mon, 3 Jul 2006, Francisco Reyes wrote: > Kostik Belousov writes: > >> I think that then 6.2 and 6.3 is not for you either. Problems >> cannot be fixed until enough information is given. > > I am trying.. but so far only other users who are having the same problem are > commenting on this and other simmilar threads. > > We just need some guidance.. > > Mark gave me a URL to turn on debugging and volunteered ot give me some > pointers.. I will try, but I will likely try on my own time, on my own > machines.. I can not tell the owner of the company I work for to let me > "try".. or "play around" in production machines.. as we loose customers > because of current problems with the 6.X line. >> Since nobody except you experience that problems (at least, only you >> notified >> about the problem existence) > > Did you miss the part of: > >> User Freebsd writes: >>> Since there are several of us experiencing what looks to be the same sort >>> of deadlock issue, I beseech you not to give up > > I am not the only one reporting or having the issue. Careful here, I think this is where things are getting confused ... the above is related to the deadlock (high vmstat blockd issue), not the NFS issue ... we're getting two different issues confused :) >> improved handling of signals in nfs client. If you could test it, that >> would be useful. > > Does it matter if the OS is i386 or am64? > Have an amd64 machine I can more easily play with... with no risk to > production. Does the amd64 machine exhibit the same problem? ---- 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