From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 09:06:59 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 B471D16A40F for ; Mon, 3 Jul 2006 09:06:59 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42052443A5 for ; Mon, 3 Jul 2006 09:06:59 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1545846BCD; Mon, 3 Jul 2006 05:06:52 -0400 (EDT) Date: Mon, 3 Jul 2006 10:06:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kostik Belousov In-Reply-To: <20060703045854.GH37822@deviant.kiev.zoral.com.ua> Message-ID: <20060703100038.I26325@fledge.watson.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> <20060703045854.GH37822@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: User Freebsd , freebsd-stable@freebsd.org, Francisco Reyes 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 09:06:59 -0000 On Mon, 3 Jul 2006, Kostik Belousov wrote: > On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote: >> Kostik Belousov writes: >>> 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. > I think you have different issues. I agree. It looks like we have several issues floating around. There are some known issues with rpc.lockd (and probably some unknown ones) that will require a concerted effort to resolve. There appear to be a number of reports relating to this/these problems. It sounds like there is also an NFS client race condition or other bug of some sort. I think it would be really useful to isolate the two during debugging. Specifically, to make sure that the second client bug is reproduceable without rpc.lockd running on the client (and related mount flags). Once we have some more information, such as vnode locking information, client thread stack traces, etc, we should probably get Mohan in the loop if things seem sticky. I believe he was on vacation last week; he may be back this week sometime. With the July 4 weekend afoot, a lot of .us developers are offline. Robert N M Watson Computer Laboratory University of Cambridge