From owner-freebsd-current Sat Jul 29 7:46:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from flow.isolve.dk (flow.isolve.dk [195.249.214.175]) by hub.freebsd.org (Postfix) with ESMTP id DE7D037B8A0 for ; Sat, 29 Jul 2000 07:46:38 -0700 (PDT) (envelope-from voland@flow.isolve.dk) Received: (from voland@localhost) by flow.isolve.dk (8.9.3/8.9.3) id QAA04837 for current@FreeBSD.ORG; Sat, 29 Jul 2000 16:45:55 +0200 (CEST) (envelope-from voland) Date: Sat, 29 Jul 2000 16:45:55 +0200 From: Vadim Belman To: current@FreeBSD.ORG Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Message-ID: <20000729164554.A4778@flow.isolve.dk> Mail-Followup-To: current@FreeBSD.ORG References: <20000728141728.A44135@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000728141728.A44135@freebsd.org>; from ache@FreeBSD.ORG on Fri, Jul 28, 2000 at 02:17:31PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 28, 2000 at 02:17:31PM -0700, Andrey A. Chernov wrote: > I too. The only way I can avoid this panic is > > 1) Remove /erc/rc.shutdown (which write files) > 2) Do several syns manually before reboot. > > In all other situations I got this panic. Just another way (suggested by a friend of my) is to shutdown into the single user mode, umount every filesystem, forcibly remount / into read-only mode - and then reboot. Gonna try putting this into /etc/rc.shutdown. -- /Voland Vadim Belman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message