Date: Tue, 22 Jul 2003 11:12:31 +0200 From: Joan Picanyol i Puig <joan@iaeste-catalunya.upc.es> To: freebsd-stable@FreeBSD.org Subject: Re: mismatching vinum configurations Message-ID: <3F1CFFFF.2090202@iaeste-catalunya.upc.es> In-Reply-To: <20030721010541.GE11810@wantadilla.lemis.com> References: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> <20030721010541.GE11810@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
En/na Greg 'groggy' Lehey ha escrit: >>What's the less traumatic way to recover the data? > I've never tried this, but a thing you could do is: > > vinum -> setdaemon 4 (turn off config updates) > vinum -> read /dev/ad0s1d (or another drive with valid config) > vinum -> start This (followed by two reboots) has worked. The reason I didn't think it was ok is that I got a wired output from 'vinum list' (wrong number of drives, *invalid* still there), how is it suposed to be useful if is not a faithful report of vinum's state? Is there another way to get the same information? tks -- pica
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F1CFFFF.2090202>