From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 07:39:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 075B516A4CE for ; Mon, 29 Mar 2004 07:39:26 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7822043D54 for ; Mon, 29 Mar 2004 07:39:25 -0800 (PST) (envelope-from kirk@strauser.com) Received: from pooh.strauser.com (pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.11/8.12.11) with ESMTP id i2TFdNEW041812 for ; Mon, 29 Mar 2004 09:39:24 -0600 (CST) (envelope-from kirk@strauser.com) To: freebsd-current@freebsd.org From: Kirk Strauser Date: Mon, 29 Mar 2004 09:39:20 -0600 Message-ID: <87k713ek7r.fsf@strauser.com> Lines: 61 X-Mailer: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' Subject: My vinum scare X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 15:39:26 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable Yesterday, I updated my system from a 5.1-CURRENT build on 2004-01-29 to recent source. All of my filesystems, except for root and swap, are on vinum volumes for flexibility in management. After the 'installkernel' step, I rebooted into single-user to make installworld and run mergemaster, and this completed successfully. Then, I rebooted to bring the system back online. That's when I discovered that vinum had totally lost all of its configuration information, except for the name of the single drive ("wd120") that I use. Following the instructions at http://www.vinumvm.org/vinum/how-to-debug.html, I got: # < log tr -d '\000-\011\200-\377' IN VINOkanga.honeypot.netwd120a>P.pMg@[obme>MBR da0 2 r0w0e0 r0w0e0 da0s4 'vinum dumpconfig' reported nothing but the definition of the "wd120" drive: no volumes, plexes, or subdisks. Nothing. At this point, I had a minor heart attack. Once I stepped back, I remembered that I *always* use 'printconfig' to write a copy of my configuration to /etc/vinum.conf. A quick 'vinum create' command had me back up and running with no ill effects. I have no idea what happened, but I ask that you trust me when I say that I hadn't touched vinum at all during the system update. Two lessons: 1) Realizing that you have a backup of such critical data as your vinum configuration is one of the best feelings in the world. 2) Realizing that in the event of failure of lesson #1, that you still have a full backup to tape from a few hours earlier, and that no matter *what* happens, you're only an hour away from having your system back... It doesn't get much better than that. =2D-=20 Kirk Strauser "94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box." --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAaEMr5sRg+Y0CpvERAm2KAJwI3DTr6cwiO1+q1ouWkjHZxYKL9ACeK9U6 lOaL/KgbRfq3CnZepGXBfnY= =crDY -----END PGP SIGNATURE----- --=-=-=--