From owner-freebsd-stable Sun Mar 16 13:52:32 2003 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 43A7C37B401 for ; Sun, 16 Mar 2003 13:52:30 -0800 (PST) Received: from smtp07.wxs.nl (smtp07.wxs.nl [195.121.6.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10F4843F75 for ; Sun, 16 Mar 2003 13:52:29 -0800 (PST) (envelope-from guusdk@planet.nl) Received: from duke.planet.nl ([80.60.89.26]) by smtp07.wxs.nl (Netscape Messaging Server 4.15) with ESMTP id HBV3FA02.4RJ for ; Sun, 16 Mar 2003 22:52:22 +0100 Message-Id: <5.2.0.9.0.20030316224954.00add738@pop.planet.nl> X-Sender: kinde084@pop.planet.nl X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sun, 16 Mar 2003 22:54:53 +0100 To: stable@freebsd.org From: Guus der Kinderen Subject: Re: Vinum Question In-Reply-To: <20030316214151.GA15646@leviathan.inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I did a little experimenting with vinum on my own, and used a (corrected) howto for vinum" >After these operations, the configuration will not be correct. It's possible you'd miss it if you abuse dumpconfig to display the configuration, but the subdisks >usr.p1.s0 and var.p1.s0 will be in empty state, and the plexes usr.p1 and var.p1 will be faulty: If I'm right, that's simmilar as what's happening to you. To fix this, do this (for the disks in the example given in that howto) >To start them, use the init command. Alternatively, modify your configuration to: > > volume usr setupstate > plex org concat > sd length 14887091s drive drive1 > plex org concat > sd length 14887091s drive drive2 > > to indicate that any discrepancies in the content can be ignored, since you will be doing a newfs on the volume. Look at this page for the entire howto: http://www.lemis.com/grog/vinum-mirrored-corrected.html - it worked for me Hope this helps, Guus At 15:41 16-3-2003 -0600, David W. Chapman Jr. wrote: >I had a drive crash on a vinum stripeset, so I put two new drives in and >decided to setup a mirror > >I noticed that only one drive was actively being used according to systat >-iostat > >doing a vinum dumpconfig it appears one of the disks was not set up properly > >What do I need to do to get the other drive back online? > >volume mirror state up >plex name mirror.p0 state up org concat vol mirror >plex name mirror.p1 state faulty org concat vol mirror >sd name mirror.p0.s0 drive d1 plex mirror.p0 len 71684096s driveoffset >265s state up plexoffset 0s >sd name mirror.p1.s0 drive d2 plex mirror.p1 len 71684096s driveoffset >265s state empty plexoffset 0s > >Thanks! > >-- >David W. Chapman Jr. >dwcjr@inethouston.net Raintree Network Services, Inc. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message