From owner-freebsd-current@FreeBSD.ORG Fri Oct 7 09:08:03 2005 Return-Path: X-Original-To: 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 8D2AA16A41F; Fri, 7 Oct 2005 09:08:03 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout2-sn1.fre.skanova.net (pne-smtpout2-sn1.fre.skanova.net [81.228.11.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22F6043D46; Fri, 7 Oct 2005 09:08:03 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.104) by pne-smtpout2-sn1.fre.skanova.net (7.2.060.1) id 43297E3C0052A637; Fri, 7 Oct 2005 11:08:02 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 7 Oct 2005 11:08:01 +0200 Content-class: urn:content-classes:message Message-ID: <4F9C9299A10AE74E89EA580D14AA10A605F55E@royal64.emp.zapto.org> X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: gvinum startup problems Thread-Index: AcXKxrN2tOfyCoK2T3O0hshk7v5D5QAVMYgg From: "Daniel Eriksson" To: Cc: Lukas Ertl Subject: RE: gvinum startup problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 09:08:03 -0000 I just tried booting with kern.geom.debugflags=3D1 and geom_vinum_load=3D"YES" in /boot/loader.conf (latest RELENG_6), and the result was not good: # gvinum list g_post_event_x(0xc0513ef0, 0xc2116600, 2, 262144) 3 drives: D vd1 State: up /dev/ad3 A: 0/117800 MB (0%) D vd0 State: up /dev/ad2 A: 0/117800 MB (0%) D vd3 State: up /dev/ad1 A: 0/117800 MB (0%) 1 volume: V 480GB State: down Plexes: 1 Size: 345 GB 1 plex: P 480GB.p0 S State: down Subdisks: 3 Size: 345 GB 4 subdisks: S 480GB.p0.s3 State: stale D: vd3 Size: 115 GB S 480GB.p0.s2 State: up D: vd2 Size: 115 GB S 480GB.p0.s1 State: up D: vd1 Size: 115 GB S 480GB.p0.s0 State: stale D: vd0 Size: 115 GB My previous assertion that it was always /dev/ad3 that failed to be tasted was probably just a matter of bad memory on my part. As you can see from the above list, one vinumdrive was never found (/dev/ad0), and two subdisks were marked as stale. Rebooting the machine without auto-start of gvinum and then manually doing a "gvinum start" from single- or multi-user brings the array up properly. I have put three logs online: 1. Normal boot, plain dmesg (just to make it easier to see what devices are found during probing, they are drowned in debug messages in the two logs below) http://193.11.63.100/normal_boot.txt 2. kern.geom.debugflags=3D1 + geom_vinum_load=3D"YES" -> single-user http://193.11.63.100/gvinum_auto_start.txt 3. kern.geom.debugflags=3D1 -> single-user -> "gvinum start" http://193.11.63.100/gvinum_manual_start.txt Warning, the two debug logs are rather long (112kB each). /Daniel Eriksson