From owner-freebsd-current Sat May 23 12:57:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21811 for freebsd-current-outgoing; Sat, 23 May 1998 12:57:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21805 for ; Sat, 23 May 1998 12:56:58 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA17339; Sat, 23 May 1998 12:56:54 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd017319; Sat May 23 12:56:53 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA10465; Sat, 23 May 1998 12:56:49 -0700 (MST) From: Terry Lambert Message-Id: <199805231956.MAA10465@usr07.primenet.com> Subject: Re: May 17th UP machine 'panic' To: michaelh@cet.co.jp (Michael Hancock) Date: Sat, 23 May 1998 19:56:49 +0000 (GMT) Cc: tlambert@primenet.com, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at May 23, 98 10:21:46 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > syncing disks... 68 51 25 done > > > panic: lockmgr: pid 26748, not exclusive lock holder 1 unlocking > > > > > > When I reported this the first time through, the comment had to do with > > > multiple CPUs...except this is a UP motherboard... > > > > > > Does anyone know why I would be getting this, or if there has been a fix > > > for it in the past 5 days that I haven't clued into on the commit list? > > > > Are you using quotas? > > > > Whoever made the recent lock changes failed to maintain the quota code > > correctly, and you will get a panic on shutdown when it tries to vput() > > the quota file that isn't being quotaoff()'ed. > > I'll take a look at this. Are you using quotas? I am, I don't know if he is. The problem is in the vput in quotaoff for the group quota file when doing a quotaoff on the user quota file. Basically, the locking semantics of vget/vput pairings have apparently become assymetric? In any case, there is a traversal of the vp's on a mount point in order to accredit all quota information correctly, and it is during this traversal that the failur occurs. This is fairly easy to reproduce; enable user and group quotas, have the quota files in the / of the FS being quota'ed, and then do a shutdown. The panic occurs during shutdown. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message