From owner-freebsd-current  Wed May 21 17:57:55 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA19206
          for current-outgoing; Wed, 21 May 1997 17:57:55 -0700 (PDT)
Received: from cc621.ntu.ac.sg (cc621.ntu.ac.sg [155.69.4.102])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA19197
          for <freebsd-current@FreeBSD.ORG>; Wed, 21 May 1997 17:57:48 -0700 (PDT)
Received: (from ktsin@localhost)
	by cc621.ntu.ac.sg (8.8.5/8.8.5) id IAA05089
	for freebsd-current@FreeBSD.ORG; Thu, 22 May 1997 08:57:12 +0800 (SGT)
Message-Id: <199705220057.IAA05089@cc621.ntu.ac.sg>
Subject: Re: Is QUOTA option broken?
In-Reply-To: <33838513.41C67EA6@MCI2000.com> from Minsung Kim at "May 21, 97 04:28:19 pm"
To: freebsd-current@FreeBSD.ORG
Date: Thu, 22 May 1997 08:57:12 +0800 (SGT)
Reply-To: ktsin@acm.org
From: Sin Key Teck <ktsin@acm.org>
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I've recently upgraded my system to current, and rebuilt the kernel.
> Everything works fine -- except the kernel goes panic whenever I
> try to halt the system (through /sbin/halt).  When the system
> boots next time, fsck -p says that all filesystems AFTER the last
> filesystem on which quota checking is enabled are clean.  And, if
> I turn off quota checking manually (quotaoff -a) and halt the
> system, it goes just fine.  No panic.

I am experiencing the same problem too. I think it has something
to do with the locking mechanism added to current. Whenever I shutdown, I'll
get a message like:

lockmgr: pid 217, not exclusive lock holder 1 unlocking

where 217 is the pid of the shutdown process.

kt