From owner-freebsd-stable@FreeBSD.ORG Sun Jul 20 13:07:28 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 7D9BC37B404 for ; Sun, 20 Jul 2003 13:07:28 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64DF543FB1 for ; Sun, 20 Jul 2003 13:07:27 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6KK7QwO001012; Sun, 20 Jul 2003 13:07:26 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6KK7QZU013315; Sun, 20 Jul 2003 13:07:26 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h6KK7Q73013314; Sun, 20 Jul 2003 13:07:26 -0700 (PDT) (envelope-from marcel) Date: Sun, 20 Jul 2003 13:07:26 -0700 From: Marcel Moolenaar To: Joan Picanyol i Puig Message-ID: <20030720200726.GB13216@dhcp01.pn.xcllnt.net> References: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> User-Agent: Mutt/1.5.4i 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, 20 Jul 2003 20:07:28 -0000 On Sun, Jul 20, 2003 at 08:27:00PM +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). The logs in da0 (barracuda) are the ones obviously > wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead > drive? Can I force vinum to use the other's drive configuration? What's > the less traumatic way to recover the data? I had the same problem twice. Also a power failure. There was no way I could fix it without trauma. I had to do the following (and I'm not joking about the reboots): WARNING: do not follow the steps below if you're not entirely sure what you're doing unless you already have nothing to lose... 1. Nuke the complete configuration, but make sure you know exactly what it was. 2. Reconfigure vinum from scratch in exactly the same way it was before. 3. Reboot the machine. I got kernel panics trying to recover my vinum volumes and that only made matters worse (it always can). 4a.For mirrored volumes you should be able to mark one drive as up, and mark the other(s) as empty (ie manually set the state). This forces a complete resync. Let it finish and reboot the machine afterwards. 4b.For RAID5 volumes you manually have to mark all disks as up and rebuild the parity. After that it's probably good to reboot the machine avoid kernel panics. Reboot twice if you're paranoid. Verify that the parity is ok! 5. fsck(8). 6. Drink lot's of alcoholic beverages to recover yourself after you verified you recovered vinum. 7. Reboot yourself. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net