Date: Sat, 2 Oct 1999 09:23:34 +0930 From: Greg Lehey <grog@lemis.com> To: FreeBSD-stable@FreeBSD.org Subject: HEADS UP! Problems upgrading Vinum to 3.3-RELEASE Message-ID: <19991002092333.A28830@freebie.lemis.com>
next in thread | raw e-mail | index | archive | help
This is a repeat of a message I sent to -questions and -hackers. As somebody pointed out, it's also a -STABLE issue. I've just found and fixed a bug in Vinum which can cause the system to crash on start. It didn't exist in 3.2, and is fixed in 3.3-STABLE. Briefly, 3.3 now allows you to put Vinum drives on any partition on any slice, and it checks these slices on start. If you don't have any slice entries (/dev/da0s1a and friends), however, it will panic after (incorrectly) reporting some subdisks to be crashed. This bug does not cause data corruption. This bug has been fixed in 3.3-STABLE. A copy of the kld is available at ftp://ftp.lemis.com/pub/vinum/vinum.ko-3.3-STABLE-30Sep1999. Note also that when upgrading from FreeBSD 3.2 to FreeBSD 3.3, you must ensure that your Vinum drives are of type Vinum. disklabel(8) should show: 3 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2048000 0 vinum # (Cyl. 0 - 1042) c: 2048000 0 unused 0 0 # (Cyl. 0 - 1042) If your partition is of type 'unused', change it with 'disklabel -e'. To find out about current bugs in Vinum, see http://www.lemis.com/vinum/bugs.html. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991002092333.A28830>