From owner-freebsd-questions@FreeBSD.ORG Tue Oct 14 22:55:52 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D14A116A4B3 for ; Tue, 14 Oct 2003 22:55:52 -0700 (PDT) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D39D43F75 for ; Tue, 14 Oct 2003 22:55:51 -0700 (PDT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id CBACC2BD37 for ; Wed, 15 Oct 2003 15:55:47 +1000 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 214C9511F9; Wed, 15 Oct 2003 15:25:46 +0930 (CST) Date: Wed, 15 Oct 2003 15:25:46 +0930 From: Greg 'groggy' Lehey To: aarong Message-ID: <20031015055546.GK13080@wantadilla.lemis.com> References: <20031015050409.GH13080@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Swj79WlilW4BQYVz" Content-Disposition: inline In-Reply-To: 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-questions@freebsd.org Subject: Re: clearing Vinum configurations X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 05:55:53 -0000 --Swj79WlilW4BQYVz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tuesday, 14 October 2003 at 22:45:02 -0700, aarong wrote: > On Tuesday, October 14, 2003, at 10:04 PM, Greg 'groggy' Lehey wrote: > >> >> I'm going to need more information on this. It doesn't correspond at >> all with my experience. Here's an example: >> ... > > I found my problem, I would obliterate a configuration and not > saveconfig. No, that's not only not necessary, it doesn't work. saveconfig saves, well, configurations. resetconfig obliterates configurations, so there's nothing left to save. > It is my experience that resetconfig will obliterate only the > configuration currently read into memory, and NOT clear the Vinum > configuration written to Vinum disks - in my case da0 and da1. As I showed in the example, you don't need a saveconfig. > On another box, again 4.8-RELEASE only with IDE instead of SCSI > drives, I completed setup and began to mirror. Without thinking I > tried to add plexes on an uninitialized drive and as such, Vinum > read the new device name beta, but listed the drive in a state of > referenced. I initialized the drive per Handbook instructions, > copied the disklabel from ad0 to ad3 (drive beta) and tried > again. After successfully starting each new plex, I saved the > config, double checked the config written to both disks with > dumpconfig, and rebooted. Upon reboot I was back to square one. I've > replicated this three times now. Did you know it takes 2 hours two > completely mirror a 69GB slice across two IDE drives? ;-) > > What I find VERY interesting is that ad3, hence known to vinum as > "beta", has the correct dumpconfig output: all plexes are "state up" > and everything is kosher. Drive "alpha", aka ad0, has the incorrect > original config where I accidently tried to create plexes on an > uninitialized drive. All *.p1 plexes are "state faulty" on "alpha" and > all the saveconfig's in the world don't seem to be changing this. I, of > course, have diligently searched the mailing lists looking for anyone > with a similar problem, only to find another guy who didn't initialize > the second drive correctly but then promptly fixed it. I'm getting confused here. A bit of the output of vinum(8) would go a long way. What does 'vinum list' say? >>> 2) why doesn't dd if=3D/dev/zero of=3D/dev/da0 seek=3D16 count=3D265 wo= rk? >>> What's in those 265 sectors that I can't touch? >> >> The second sector on the disk is protected. You can't write to it. >> If you start at sector 2, it will work. >> >> The Vinum label is at sector 8. That's the only sector you need to >> clear to manually obliterate a Vinum configuration. > > Then the command should look something like: dd if=3D/dev/zero > of=3D/dev/da0 seek=3D18 count=3D263 ? =20 No,=20 > Sector eight after the sixteen sector bootstrap, correct? No. Just sector 8: dd if=3D/dev/zero of=3D/dev/da0 seek=3D8 count=3D1 But you shouldn't need that. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. --Swj79WlilW4BQYVz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/jOFiIubykFB6QiMRAk1yAJkBoyw1ggSdlXwbt+CWOoyQW5xpyACePDit y4ngXPKSoZqsoklLwifMlXw= =2x06 -----END PGP SIGNATURE----- --Swj79WlilW4BQYVz--