From owner-freebsd-stable@FreeBSD.ORG Fri Oct 8 11:52:15 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 6B69F16A4CE for ; Fri, 8 Oct 2004 11:52:15 +0000 (GMT) Received: from gate.ka.punkt.de (gate.ka.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D34643D41 for ; Fri, 8 Oct 2004 11:52:14 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by gate.ka.punkt.de with ESMTP id i98BooWP015784 for ; Fri, 8 Oct 2004 13:50:50 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id i98BqDPf025069 for ; Fri, 8 Oct 2004 13:52:13 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id i98BqDgb025068 for freebsd-stable@freebsd.org; Fri, 8 Oct 2004 13:52:13 +0200 (CEST) (envelope-from ry93) From: "Patrick M. Hausen" Message-Id: <200410081152.i98BqDgb025068@hugo10.ka.punkt.de> To: freebsd-stable@freebsd.org Date: Fri, 8 Oct 2004 13:52:13 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: 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 11:52:15 -0000 Hi all! We have a production system that runs on a vinum system drive configured like this: cab# vinum l 2 drives: D b State: up /dev/ad1s1h A: 0/114494 MB (0%) D a State: up /dev/ad0s1h A: 0/114494 MB (0%) 4 volumes: V root State: up Plexes: 2 Size: 256 MB V swap State: up Plexes: 2 Size: 3072 MB V usr State: up Plexes: 2 Size: 4096 MB V var State: up Plexes: 2 Size: 104 GB 8 plexes: P root.p1 C State: up Subdisks: 1 Size: 256 MB P swap.p1 C State: up Subdisks: 1 Size: 3072 MB P usr.p1 C State: up Subdisks: 1 Size: 4096 MB P var.p1 C State: up Subdisks: 1 Size: 104 GB P root.p0 C State: up Subdisks: 1 Size: 256 MB P swap.p0 C State: up Subdisks: 1 Size: 3072 MB P usr.p0 C State: up Subdisks: 1 Size: 4096 MB P var.p0 C State: up Subdisks: 1 Size: 104 GB 8 subdisks: S root.p1.s0 State: up D: b Size: 256 MB S swap.p1.s0 State: up D: b Size: 3072 MB S usr.p1.s0 State: up D: b Size: 4096 MB S var.p1.s0 State: up D: b Size: 104 GB S root.p0.s0 State: up D: a Size: 256 MB S swap.p0.s0 State: up D: a Size: 3072 MB S usr.p0.s0 State: up D: a Size: 4096 MB S var.p0.s0 State: up D: a Size: 104 GB 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. Thanks, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de