From owner-freebsd-fs@FreeBSD.ORG Tue Mar 9 13:42:40 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3422116A4DB for ; Tue, 9 Mar 2004 13:42:40 -0800 (PST) Received: from mxsf11.cluster1.charter.net (mxsf11.cluster1.charter.net [209.225.28.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id A24FC43D31 for ; Tue, 9 Mar 2004 13:42:39 -0800 (PST) (envelope-from ups@tree.com) Received: from stups.com ([209.187.143.11])i29La7Dx091585; Tue, 9 Mar 2004 16:36:07 -0500 (EST) (envelope-from ups@tree.com) Received: from tree.com (localhost [127.0.0.1]) by stups.com (8.9.3/8.9.3) with ESMTP id QAA05388; Tue, 9 Mar 2004 16:36:07 -0500 Message-Id: <200403092136.QAA05388@stups.com> X-Mailer: exmh version 2.0.2 To: rick@snowhite.cis.uoguelph.ca In-Reply-To: Message from rick@snowhite.cis.uoguelph.ca <200403052250.RAA68715@snowhite.cis.uoguelph.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Mar 2004 16:36:07 -0500 From: Stephan Uphoff cc: freebsd-fs@freebsd.org Subject: Re: newnfsd's stuck on "ufs" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 21:42:40 -0000 Hi, This sound familiar. Somewhere your NFSv4 server forgets to unlock a vnode. Since ufs uses a recursive lock - this does not block the thread forgetting the unlock. I solved similar problems (netbsd, home made lock manager and file system) by adding "No vnode lock held" assertions to the nfs server loop. Let me know if I can help - I am really interested in seeing NFSv4 in FreeBSD. Stephan > I'm working away at porting my NFSv4 server to FreeBSD5.2. It goes along > ok for a while, but when doing several ops concurrently, most of the nfsd > threads end up stuck sleeping on "ufs" as shown by the attached "ps axl". > (The amusing part is that, once all but one thread is stuck, the last > thread works fine. In other words, the "fix" is to only run one newnfsd:-) > > Anybody happen to know off the top of head, what I've screwed up? > > Thanks for any hints, rick > --- ps axl of newnfsd --- > 0 523 522 0 4 0 1192 736 nfsd I ?? 0:05.34 newnfsd: ser > 0 524 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 525 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 526 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 527 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 528 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 529 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 530 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 531 522 0 -4 0 1192 736 ufs D ?? 0:00.02 newnfsd: ser > 0 532 522 0 4 0 1192 736 nfsd I ?? 0:00.01 newnfsd: ser > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >