From owner-freebsd-stable@FreeBSD.ORG Sat Aug 2 18:53:44 2003 Return-Path: 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 4347B37B401 for ; Sat, 2 Aug 2003 18:53:44 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADCA343F93 for ; Sat, 2 Aug 2003 18:53:42 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id ACEB2526A4; Sun, 3 Aug 2003 11:23:40 +0930 (CST) Date: Sun, 3 Aug 2003 11:23:40 +0930 From: Greg 'groggy' Lehey To: Joan Picanyol i Puig Message-ID: <20030803015340.GP95375@wantadilla.lemis.com> References: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> <20030721010541.GE11810@wantadilla.lemis.com> <3F1CFFFF.2090202@iaeste-catalunya.upc.es> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9+VnUxDxRuy97YQ+" Content-Disposition: inline In-Reply-To: <3F1CFFFF.2090202@iaeste-catalunya.upc.es> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-stable@FreeBSD.org Subject: Re: mismatching vinum configurations X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Aug 2003 01:53:44 -0000 --9+VnUxDxRuy97YQ+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 22 July 2003 at 11:12:31 +0200, Joan Picanyol i Puig wrote: > 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? No. If you get that kind of message, something has gone wrong. I've already given details of how to track down this kind of problem. If you want a reply from me, please include my name in the To: list. Otherwise it can take a long time before I see it. Greg -- See complete headers for address and phone numbers --9+VnUxDxRuy97YQ+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/LGskIubykFB6QiMRAn7YAJ99WC9EK+vgZTBU/kYEGjFapeo5HwCeKwXP lQtDUDyKY3WI8l50VGGQQU0= =12kR -----END PGP SIGNATURE----- --9+VnUxDxRuy97YQ+--