From owner-freebsd-questions@FreeBSD.ORG Thu Nov 11 12:11:14 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E98B616A4CE for ; Thu, 11 Nov 2004 12:11:14 +0000 (GMT) Received: from posti5.jyu.fi (posti5.jyu.fi [130.234.4.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4484843D68 for ; Thu, 11 Nov 2004 12:11:14 +0000 (GMT) (envelope-from tristan@cc.jyu.fi) Received: from silmu.st.jyu.fi (silmu.st.jyu.fi [130.234.4.64]) iABCB8RG014682; Thu, 11 Nov 2004 14:11:08 +0200 Date: Thu, 11 Nov 2004 14:11:02 +0200 (EET) From: Kim Helenius X-X-Sender: tristan@silmu.st.jyu.fi To: Artem Kazakov In-Reply-To: <41934430.9020000@comptek.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at posti5.jyu.fi; Thu, 11 Nov 2004 14:11:09 +0200 X-Spam-Checked: by miltrassassin at posti5.jyu.fi; Thu, 11 Nov 2004 14:11:09 +0200 cc: freebsd-questions@freebsd.org Subject: Re: Vinum configuration lost at vinum stop / start X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 12:11:15 -0000 On Thu, 11 Nov 2004, Artem Kazakov wrote: > Kim Helenius wrote: > > > Now I can newfs /dev/vinum/vinum0, mount it, use it, etc. But when I do > > vinum stop, vinum start, vinum stop, and vinum start something amazing > > happens. Vinum l after this is as follows: > > > > 2 drives: > > D d2 State: up /dev/ad5s1d A: 286181/286181 > > MB (100%) > > D d1 State: up /dev/ad4s1d A: 286181/286181 > > MB (100%) > > > > 0 volumes: > > 0 plexes: > > 0 subdisks: > > > > Where did my configuration go?! I can of course recreate it, with no > > data lost, but imagine this on a raid5 where the plex goes into init > > mode after creation. Not a pleasant scenario. Also recreating the > > configuration from a config file after every reboot doesn't sound > > interesting. > you shoud issue a read command to vinum to make it read configureation. > in your case: > vinum read /dev/ad5 /dev/ad4 Thank you for your answer. However, when I mentioned the configuration is lost, it is lost and not stored on the drives anymore. Thus 'vinum read' command cannot read it from the drives. In addition, 'vinum start' scans drives for vinum information so in fact 'vinum read' should not be needed. > -- > Kazakov Artem > > OOO "CompTek" > tel: +7(095) 785-2525, ext.1802 > fax: +7(095) 785-2526 > WWW: http://www.comptek.ru >