From owner-freebsd-current@FreeBSD.ORG Sun Oct 9 15:58:26 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 1FF4116A41F; Sun, 9 Oct 2005 15:58:26 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABD4F43D64; Sun, 9 Oct 2005 15:58:23 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.104) by pne-smtpout1-sn1.fre.skanova.net (7.2.060.1) id 43200DEA00651883; Sun, 9 Oct 2005 17:58:22 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 9 Oct 2005 17:58:22 +0200 Content-class: urn:content-classes:message Message-ID: <4F9C9299A10AE74E89EA580D14AA10A605F562@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: AcXKxrN2tOfyCoK2T3O0hshk7v5D5QAVMYggAHNosSA= 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: Sun, 09 Oct 2005 15:58:26 -0000 After the gvinum MFCs earlier today there has been some regression in the RELENG_6 branch. Starting gvinum manually works, but no device node is created (no /dev/gvinum dir at all). This means the array cannot be used. As before, auto-loading gvinum results in a broken array. Right after probing the ATA disks, the following message is printed on the console: GEOM_VINUM: subdisk 480GB.p0.s3 state change: down -> stale GEOM_VINUM: subdisk 480GB.p0.s0 state change: down -> stale This of course results in a broken array: # gvinum list 4 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%) D vd2 State: up /dev/ad0 A: 0/117800 MB (0%) 1 volume: V 480GB State: down Plexes: 1 Size: 460 GB 1 plex: P 480GB.p0 S State: down Subdisks: 4 Size: 460 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 Manually doing "gvinum setstate up 480GB.p0.s0" and gvinum setstate up 480GB.p0.s3" brings the array back online, and it can be used as normal (fsck and mount). If gvinum really is this broken, shouldn't it be removed from RELENG_6? Or is this just something local on my setup? Oh, and there is still no manpage for gvinum. /Daniel Eriksson