Date: Tue, 17 Feb 2004 16:11:59 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: Lukas Ertl <l.ertl@univie.ac.at> Subject: Re: Can't save Vinum config: No such file or directory Message-ID: <20040217151159.GA35012@pcwin002.win.tue.nl> In-Reply-To: <20040216231325.GP33797@wantadilla.lemis.com> References: <20040213130520.GB714@pcwin002.win.tue.nl> <20040213175748.B662@korben.in.tern> <20040213173456.GH714@pcwin002.win.tue.nl> <20040213201416.E662@korben.in.tern> <20040213205311.GI714@pcwin002.win.tue.nl> <20040213235341.L618@korben.in.tern> <20040216110935.GA753@pcwin002.win.tue.nl> <20040216231325.GP33797@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 17, 2004 at 09:43:25AM +1030, Greg 'groggy' Lehey wrote: > Sorry, yes, I was going to reply to the previous message. The > dumpconfig output suggest that everything has been overwritten. I > fear this is the result of something like doing a saveconfig when > there was nothing to save. That's probably what happened then. > > Although the data that was on the volume is not crucial, it would be > > nice if there was a way to recover it; so if you don't want to > > investigate further, can you tell me whether a vinum create would > > restore my volumes, >=20 > Yes, it should. The data should be unchanged, so the file system > should still be OK. Great, this appeared to work, albeit with one little 'annoyance' -- vinum won't save it's configuration to the disk anymore. A 'vinum saveconfi= g' doesn't produce error messages but a vinum stop / vinum start later and my volume is gone again. The data stays intact. No problem though, I'll restart with a clean volume once the data is safe (most likely ccd though I haven't heard yet whether that is safe). > > or is there simply no way that I can do so without obliterating the > > data? If the latter, I'll just move on and recreate the plex using > > ccd(4) (seeing as following vinum development is not one of my goals > > right now). >=20 > It occurs to me that we could easily prevent this kind of problem in > the future by saving the Vinum configuration at boot time to > /var/run/vinum.conf.boot or some such. It would obviously make sense > to keep the previous configuration as well. This should be a pretty > trivial modification to the startup scripts. Yes, I was lucky that I kept my original configuration. This might be a nice safeguard. Thanks for your & Lukas' time, sorry for the false alarm, --Stijn --=20 "...I like logs. They give me a warm fuzzy feeling. I've been known to keep logs for 30 months at a time (generally when I thought I was rotating them daily, but was actually rotating them once a month)." -- Michael Lucas, in Big Scary Daemons article 'Controlling Bandwidth' --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAMi8/Y3r/tLQmfWcRAqdNAJ43UdzrtO0Xil+5OSRaPpNf3AmRFwCdF5KU nIPJ2/2ESP7/cUl9guYnm+4= =cVQi -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040217151159.GA35012>