From owner-freebsd-current Wed Sep 4 19:15:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA14473 for current-outgoing; Wed, 4 Sep 1996 19:15:04 -0700 (PDT) Received: from janai.thuvia.org (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA14461 for ; Wed, 4 Sep 1996 19:14:59 -0700 (PDT) Received: (from mark@localhost) by janai.thuvia.org (8.7.5/8.7.3) id DAA15778; Thu, 5 Sep 1996 03:14:47 +0100 (BST) Message-Id: <199609050214.DAA15778@janai.thuvia.org> From: mark@linus.demon.co.uk (Mark Valentine) Date: Thu, 5 Sep 1996 03:14:47 +0100 In-Reply-To: Robin Cutshaw's message of Sep 4, 5:46pm X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Robin Cutshaw , current@freebsd.org Subject: Re: nfs related panic Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: Robin Cutshaw > Date: Wed 4 Sep, 1996 > Subject: nfs related panic > Running 2.2-960801-SNAP or current-smp with 1 or 2 cpu's active I get: > > panic : ufs_ihashget:recursive lock not expected -- pid 155 > > when running two or more nfs clients off of this box as a server (and > building XFree86 312G remotely). Changing the number of nfsd's running > had no effect. > > Fixed in -current? No, but Doug Rabson posted a fix that does the trick to the hackers list back in July (I just tracked it down and duly submitted it to the gnats system after stumbling over the bug at work today). It's reported to work with SunOS 5.5 and OSF/1 NFSv3 clients. Cheers, Mark. (This version of the fix is against rev. 1.32 of sys/nfs/nfs_serv.c.) --- nfs_serv.c.ctm Mon Sep 2 23:44:18 1996 +++ nfs_serv.c Wed Sep 4 22:55:23 1996 @@ -2899,6 +2899,7 @@ nfsm_srvpostop_attr(getret, &at); return (0); } + vput(nvp); dirlen = len = NFSX_V3POSTOPATTR + NFSX_V3COOKIEVERF + 2 * NFSX_UNSIGNED; nfsm_reply(cnt); -- Mark Valentine at Home