From owner-freebsd-questions Wed Sep 29 18: 4:45 1999 Delivered-To: freebsd-questions@freebsd.org Received: from inet.chip-web.com (c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (Postfix) with SMTP id 83B9615287 for ; Wed, 29 Sep 1999 18:04:40 -0700 (PDT) (envelope-from ludwigp@bigfoot.com) Received: (qmail 14819 invoked from network); 30 Sep 1999 01:03:54 -0000 Received: from inet.chip-web.com (HELO bigfoot.com) (root@172.16.1.5) by inet.chip-web.com with SMTP; 30 Sep 1999 01:03:54 -0000 Message-ID: <37F2B6E9.98144B33@bigfoot.com> Date: Wed, 29 Sep 1999 18:03:37 -0700 From: Ludwig Pummer X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eric J. Schwertfeger" Cc: freebsd-questions@freebsd.org Subject: Re: vinum and 3.2R -> 3.3R upgrade References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Eric J. Schwertfeger" wrote: > > Upgraded a 3.2R storage server to 3.3R, and the machine didn't see the > existing vinum slices, which was to be expected since I hadn't changed the > slices from "unused" to "vinum". Well, I made that change, and now the > same machine comes up with several errors (claiming at least one of the > slices is unavailable, so the concatination is corrupted), then a kernel > panic. > > For the time being, I'm running 3.3R user space, and 3.2R kernel, which > makes me uncomfortable. > > I'm preparing to back it up now, to reinitialize vinum and restore, but > I was curious as to if anyone else had seen this and had a quicker > solution, as I really don't want to be down for the length of time it will > take to back up and restore 14GB of data. > > Yeah, I know, should have done it right in the first place :-) I had that problem when upgrading a 3.1-STABLE machine to 3.3-STABLE. I don't remember the exact process anymore, but the system is working fine and vinum doesn't list any bad volumes/plexes/subdisks. I fixed the disklabel in single user mode (took some work because /usr and /var are vinum volumes), rebooted, did a 'vinum makedev' (in single user mode) and rebooted. I think after that last time, it came up OK. --Ludwig Pummer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message