Date: Thu, 11 Nov 2004 14:11:02 +0200 (EET) From: Kim Helenius <tristan@cc.jyu.fi> To: Artem Kazakov <a.kazakov@comptek.ru> Cc: freebsd-questions@freebsd.org Subject: Re: Vinum configuration lost at vinum stop / start Message-ID: <Pine.LNX.4.44.0411111408310.13250-100000@silmu.st.jyu.fi> In-Reply-To: <41934430.9020000@comptek.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44.0411111408310.13250-100000>