From owner-freebsd-bugs Mon May 21 5:59:59 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 89E2837B424; Mon, 21 May 2001 05:59:56 -0700 (PDT) (envelope-from dwmalone@FreeBSD.org) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f4LCxuG19847; Mon, 21 May 2001 05:59:56 -0700 (PDT) (envelope-from dwmalone) Date: Mon, 21 May 2001 05:59:56 -0700 (PDT) From: Message-Id: <200105211259.f4LCxuG19847@freefall.freebsd.org> To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org, grog@FreeBSD.org Subject: Re: misc/27498: vinum crashed after 'vinum dumpconfig' Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: vinum crashed after 'vinum dumpconfig' Responsible-Changed-From-To: freebsd-bugs->grog Responsible-Changed-By: dwmalone Responsible-Changed-When: Mon May 21 05:53:13 PDT 2001 Responsible-Changed-Why: I tried to reproduce the problem here on a machine and I think I managed to (tared /usr to the vinum disk and kept doing "vinum dumpconfig"), so it looks easy enough to reproduce. Grog is likely to have a better idea of what the problem is, but if you could rerun gdb on the vmcore and send us the output of "trace" it would probably help. (I'll try to get a trace from the machine I just killed once I'm closer to it). David. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27498 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message