From owner-freebsd-current@FreeBSD.ORG  Tue Jun 29 18:55:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 24B4816A4CE; Tue, 29 Jun 2004 18:55:55 +0000 (GMT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 672EC43D45; Tue, 29 Jun 2004 18:55:54 +0000 (GMT)
	(envelope-from don@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <MTR29NS8>; Tue, 29 Jun 2004 14:55:49 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337051D914D@mail.sandvine.com>
From: Don Bowman <don@sandvine.com>
To: 'Brian Fundakowski Feldman' <green@FreeBSD.org>,
	Daniel Lang <dl@leo.org>
Date: Tue, 29 Jun 2004 14:55:48 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
cc: freebsd-current@FreeBSD.org
cc: John Baldwin <jhb@FreeBSD.org>
Subject: RE: kern/68442: panic - acquiring duplicate lock of same type: "s
	leepq chain"
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2004 18:55:55 -0000

From: Brian Fundakowski Feldman [mailto:green@FreeBSD.org]
 ...

> > 
> > (What hurts most, is, that in one occasion I had a ddb prompt
> > and could call doadump() successfully. But after reboot, damn 
> > /var was full, so savecore could not write it to disk, argl!).
> 
> You can make /var/crash a symlink to a directory with more space.
> 

Happens to me all the time. When the machine comes back
up, make some space somewhere, and just run savecore
again (with force if needed), you'll usually get a good
core.