From owner-freebsd-questions@FreeBSD.ORG Tue Nov 16 06:21:09 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 748FD16A4CE for ; Tue, 16 Nov 2004 06:21:09 +0000 (GMT) Received: from turing.cs.hmc.edu (turing.cs.hmc.edu [134.173.42.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 532B243D5F for ; Tue, 16 Nov 2004 06:21:08 +0000 (GMT) (envelope-from mac@cs.hmc.edu) Received: by turing.cs.hmc.edu (Postfix, from userid 34126) id 370DC5337A; Mon, 15 Nov 2004 22:21:08 -0800 (PST) Date: Mon, 15 Nov 2004 22:21:08 -0800 From: Mac Mason To: freebsd-questions@freebsd.org Message-ID: <20041116062107.GA15521@turing.cs.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: /boot/loader.conf not fixing vinum issue X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: mac@cs.hmc.edu List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 06:21:09 -0000 I have two vinum volumes on my system; one, a mirrored volume, is /usr, and the other is mounted to /usr/storage. After updating to 5.3-RELEASE, boot into multi-user mode fails with a dangling vnode panic. According to the Errata: (31 Oct 2004, updated on 12 Nov 2004) The vinum(4) subsystem works on 5.3, but it can cause a system panic at boot time. As a workaround you can add vinum_load="YES" to /boot/loader.conf. So I did that. And it doesn't fix it. Using gvinum seems like a really bad idea at the moment, given that it's only about half-done. What should I try next? Thanks! --Mac -- Julian "Mac" Mason mac@cs.hmc.edu Computer Science '06 (909)-607-3129 Harvey Mudd College