From owner-freebsd-current Sat May 23 06:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24339 for freebsd-current-outgoing; Sat, 23 May 1998 06:22:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24332 for ; Sat, 23 May 1998 06:22:55 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id NAA01522; Sat, 23 May 1998 13:21:46 GMT Date: Sat, 23 May 1998 22:21:46 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: May 17th UP machine 'panic' In-Reply-To: <199805230124.SAA22740@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 May 1998, Terry Lambert wrote: > > 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? Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message