From owner-freebsd-stable@FreeBSD.ORG Sun Jul 20 18:05:45 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 A64C137B401 for ; Sun, 20 Jul 2003 18:05:45 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id D261B43F3F for ; Sun, 20 Jul 2003 18:05:43 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id B9292526A9; Mon, 21 Jul 2003 10:35:41 +0930 (CST) Date: Mon, 21 Jul 2003 10:35:41 +0930 From: Greg 'groggy' Lehey To: Joan Picanyol i Puig Message-ID: <20030721010541.GE11810@wantadilla.lemis.com> References: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rErXCrER28iYcLtG" Content-Disposition: inline In-Reply-To: <3F1ADEF4.3040306@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: Mon, 21 Jul 2003 01:05:45 -0000 --rErXCrER28iYcLtG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sunday, 20 July 2003 at 20:27:00 +0200, Joan Picanyol i Puig wrote: > Hi, > > I had a power failure, and the on-disk configuration for vinum went > bizarre. The logs read from disks are at http://biaix.org/pk/debug/ > (log.$DEVICE files).=20 They're not much help, and a lot of the files are inaccessible. The output of 'vinum dumpconfig' would be easier. > The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty > sure the others are ok. Is this a 'virtually' dead drive? It's not a hardware problem, if that's what you mean. > Can I force vinum to use the other's drive configuration? Yes. > 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 could bring back your entire configuration. If anything goes wrong, it's not serious, because the config updates are turned off. Why do you have two drives on each SCSI disk? > Most of the data is mirrored over da0 & da1, but I can't start any of > the mirrored volumes (I get 'Drive is down') What should I do to access > the mirrored volumes? If 'start' above doesn't work, you can try running a Vinum config file like: drive barracuda device /dev/da0s1f Let me know how it works out. Greg -- See complete headers for address and phone numbers --rErXCrER28iYcLtG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/GzxlIubykFB6QiMRAgssAJ9t8Q2TCqjdgCyscifKU13igrkw0gCdHsfV 4bYj7jiFOk6nZ3051JP84Bk= =6s90 -----END PGP SIGNATURE----- --rErXCrER28iYcLtG--