From owner-freebsd-current@FreeBSD.ORG Wed Sep 1 15:32:30 2004 Return-Path: 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 0443516A4CE for ; Wed, 1 Sep 2004 15:32:30 +0000 (GMT) Received: from digitalfreaks.org (digitalfreaks.org [216.151.95.156]) by mx1.FreeBSD.org (Postfix) with SMTP id 97B5F43D41 for ; Wed, 1 Sep 2004 15:32:29 +0000 (GMT) (envelope-from ziccardi@digitalfreaks.org) Received: (qmail 62094 invoked by uid 1000); 1 Sep 2004 15:32:11 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Sep 2004 15:32:11 -0000 Date: Wed, 1 Sep 2004 11:32:11 -0400 (EDT) From: Chad Ziccardi To: current@freebsd.org In-Reply-To: <20040831211626.L9079@digitalfreaks.org> Message-ID: <20040901113049.M61763@digitalfreaks.org> References: <20040831054536.D46320@digitalfreaks.org> <20040831211626.L9079@digitalfreaks.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Thu, 02 Sep 2004 11:53:01 +0000 Subject: Re: vinum root issue on 5.3-Beta2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 01 Sep 2004 15:32:30 -0000 begin quote from Chad Ziccardi written 2004-08-31: Problem fixed using geom_vinum instead of the vinum module, and switching everything over to gvinum. > just an additional note to this, if I boot it the 1st way, and add a new set > of drives (mirror -n m-usr -v /dev/ad0s1d /dev/ad2s1d) it does that one > correctly, again.. until I reboot using that setup, which the vinumdriveX > associated with /dev/ad2 all show referenced. > > begin quote from Chad Ziccardi written > 2004-08-31: > >> >> I'm working on setting up a mirrored root filesystem as explained in: >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html >> >> I've gotten it to boot then noticed something broken about it on my setup. >> >> More info on my setup is at the bottom of this message. >> >> If it boots to the vinum partition it does not properly load vinum. >> How to explain that better.. >> booting normal as described in the handbook (loader.conf settings) >> it appears to only read ad0s1h for data, thus never fully comes up. >> >> I get among the various warnings (a slice is missing!) >> >> vinum: incompatible sector sizes. m-root.p1 has 0, m-root has 512. >> Ignored. >> Mounting root from ufs:/dev/vinum/m-root >> vinum -> ld >> D vinumdrive0 State: up /dev/ad0s1h A: 0/1023 MB (0%) >> D vinumdrive1 State: referenced unknown A: 0/0 MB >> since it can't see vinumdrive1 the plex and subdisks are faulty. >> >> >> >> >> However booting to the a slice without using vinum (removed from >> loader.conf) >> booted up on ad0s1a(or ad0s1h)(half of the mirror) >> >> then doing vinum start after logging in I get: >> >> vinum: reading configuration from /dev/ad2s1h >> vinum: updating configuration from /dev/ad0s1h >> Aug 31 05:55:06 kernel: vinum: reading configuration from /dev/ad2s1h >> Aug 31 05:55:06 kernel: vinum: updating configuration from /dev/ad0s1h >> >> vinum -> ld >> D vinumdrive1 State: up /dev/ad2s1h A: 0/1023 MB (0%) >> D vinumdrive0 State: up /dev/ad0s1h A: 0/1023 MB (0%) >> >> >> >> Is this a known issue? Is there something wrong with how I've set it up? -- Chad Ziccardi, Professional Slacker cz@digitalfreaks.org "Some cause happiness wherever they go; others whenever they go."