From owner-freebsd-stable@FreeBSD.ORG Fri Oct 8 15:53:06 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 869E616A4CE for ; Fri, 8 Oct 2004 15:53:06 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F54B43D48 for ; Fri, 8 Oct 2004 15:53:06 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from hawkwind.Chelsea-Ct.Org (pool-151-199-91-61.roa.east.verizon.net [151.199.91.61]) by gromit.dlib.vt.edu (8.13.1/8.13.1) with ESMTP id i98Fr3hd098140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 8 Oct 2004 11:53:05 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: from [192.168.1.25] (zappa [192.168.1.25])i98Fquh4017305; Fri, 8 Oct 2004 11:52:57 -0400 (EDT) From: Paul Mather To: "Patrick M. Hausen" In-Reply-To: <200410081152.i98BqDgb025068@hugo10.ka.punkt.de> References: <200410081152.i98BqDgb025068@hugo10.ka.punkt.de> Content-Type: text/plain Message-Id: <1097250775.3237.28.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 08 Oct 2004 11:52:56 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: Vinum problems in 5.3-BETA7? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2004 15:53:06 -0000 On Fri, 2004-10-08 at 07:52, Patrick M. Hausen wrote: > We have a production system that runs on a vinum system drive > configured like this: [[Configuration omitted.]] > It's currently running fine with FreeBSD 5.2.1-RELEASE-p10. > > After upgrading to 5.3-BETA7, buildworld, buildkernel, installkernel > and reboot the system stops: > > vinum: loaded > vinum: no drives found > > That's it. Of course it complains that it can't mount /dev/vinum/root. > > The list of detected GEOM devices at the "mountroot> " prompt > includes ad0s1h, ad1s1h, ad0s1, ad1s1, ad0, ad1 and some more > partitions. > > > Where do I go from here? Is this expected behaviour due to the ongoing > GEOM changes or should I go read Greg's "how to debug vinum problems" > document? I will do that, no problem. Just want to know if it makes > sense at all, because now everyone might tell me "vinum is known broken in > 5.3" or similar. Vinum is known broken in 5.3. :-) You should be using geom_vinum instead. It will largely be a drop-in replacement for your above Vinum configuration. (I am using it on a similar root-on-vinum setup.) The main changes are these: 1) Load "geom_vinum" in /boot/loader.conf, e.g., add 'geom_vinum_load="YES"' to /boot/loader.conf. This will auto-detect your Vinum on-disk configuration during boot. You don't need any rc.conf glue with geom_vinum. 2) Change "vinum" to "gvinum" in /etc/fstab. E.g., use "/dev/gvinum/root" instead of "/dev/vinum/root" 3) The userland utility is "gvinum" instead of "vinum". I am using geom_vinum on a root-on-vinum configuration under 6-CURRENT since before RELENG_5 was branched, and I believe the same holds true for RELENG_5 and HEAD as far as the above three points are concerned. I don't know if there are plans to replace vinum entirely with gvinum (and drop the "g" prefix) for 5.3-RELEASE. Lukas Ertl would know. Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa