From owner-freebsd-stable Fri Jan 5 18:12:23 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 18:12:19 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 48DD137B69C for ; Fri, 5 Jan 2001 18:12:13 -0800 (PST) Received: from [172.17.1.121] (warp-core.skynet.be [195.238.2.25]) by trinity.skynet.be (Postfix) with ESMTP id 91DFF18455; Sat, 6 Jan 2001 03:12:02 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20010106122304.I48589@wantadilla.lemis.com> References: <20010106122304.I48589@wantadilla.lemis.com> Date: Sat, 6 Jan 2001 03:11:20 +0100 To: Greg Lehey From: Brad Knowles Subject: Re: Problems with corrupted vinum devices... Cc: Andy De Petter , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:23 PM +1030 2001/1/6, Greg Lehey wrote: > Well, I've taken a look at the log file, and in fact all the drives > except the first two have "NO VINO", which is the magic number for > deleted Vinum drives. This is probably the result of a resetconfig, > and it completely explains the following problems. I counted only four instances of "NO VINO", which I take to mean that the old devices (da4s1, da4s2, da5s1, and da5s2) were all relatively clean, while the new devices were all corrupt. > I've just checked the source code, and it looks as if I don't log > whether the configuration updates are enabled at all. There's no > reason to think that they should not be based on the other information > you give, but evidently we never got the configuration to disk. Did > you get any error messages? No, everything seemed to work just fine -- vinum showed the sub disks, plexes, and volumes as being up, I could create filesystems, etc.... > Anyway, the good news is that the data is almost certainly still > there. You should be able to recreate the volumes with the same > configuration file you used the first time round (don't use > resetconfig first). If the second plexes were up when the system > crashed, you should use the setupstate keyword for the volumes to > indicate that. Well, we've already deleted and re-created the devices once, and now we can't even get vinum to start because it can't read the supposedly existing devices. I am at a loss to understand how we would recreate the devices another time, on top of the old configurations (and hopefully be able to retain all the data, etc...). Is there something I'm missing? Maybe you could explain this process in a little more detail? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message