From owner-freebsd-questions Wed Sep 29 8: 8:49 1999 Delivered-To: freebsd-questions@freebsd.org Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (Postfix) with ESMTP id A534814FD5 for ; Wed, 29 Sep 1999 08:08:18 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.3/8.9.3) with ESMTP id IAA13892 for ; Wed, 29 Sep 1999 08:08:18 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Wed, 29 Sep 1999 08:08:17 -0700 (PDT) From: "Eric J. Schwertfeger" To: questions@freebsd.org Subject: vinum and 3.2R -> 3.3R upgrade Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message