From owner-freebsd-bugs@FreeBSD.ORG Sat Jul 24 18:20:18 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 087A616A4CE for ; Sat, 24 Jul 2004 18:20:17 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD41C43D31 for ; Sat, 24 Jul 2004 18:20:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i6OIKDJw033542 for ; Sat, 24 Jul 2004 18:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6OIKDNj033541; Sat, 24 Jul 2004 18:20:13 GMT (envelope-from gnats) Date: Sat, 24 Jul 2004 18:20:13 GMT Message-Id: <200407241820.i6OIKDNj033541@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jens Schweikhardt Subject: Re: kern/68698: vinum(4) broken in 5.2-current X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jens Schweikhardt List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jul 2004 18:20:18 -0000 The following reply was made to PR kern/68698; it has been noted by GNATS. From: Jens Schweikhardt To: GNATS Bug Followup Cc: Subject: Re: kern/68698: vinum(4) broken in 5.2-current Date: Sat, 24 Jul 2004 20:15:51 +0200 I can confirm that setting start_cmd="mount /;vinum start" in /etc/rc.d/vinum is a workaround. The panic is gone. So it appears that "vinum start" has gained the prerequisite of a mounted rootfs... Can vinum experts confirm or deny this? Could automounting / if it's missing be added to "vinum start" or is this the wrong way to fix the issue? Jens