Date: Sat, 13 Mar 1999 09:00:46 +1030 From: Greg Lehey <grog@lemis.com> To: Brad Knowles <blk@skynet.be>, Philip Kizer <pckizer@nostrum.com> Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Vinum questions? Message-ID: <19990313090046.F429@lemis.com> In-Reply-To: <19990312191604.015850@relay.skynet.be>; from Brad Knowles on Fri, Mar 12, 1999 at 07:16:04PM %2B0100 References: <199903121426.IAA06485@mail.nostrum.com> <19990312191604.015850@relay.skynet.be>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 12 March 1999 at 19:16:04 +0100, Brad Knowles wrote: > On Fri, Mar 12, 1999, Philip Kizer <pckizer@nostrum.com> wrote: > >> I then did a 'vinum create /etc/vinum.conf' with the following config file: > > I got the disklabels working correctly, but I'm still having > problems. The following /etc/vinum.cf file doesn't work correctly: > > # /etc/vinum.cf - config file for vinum(8) > # > # Our drives > drive d1 device /dev/da1e > drive d2 device /dev/da2e > drive d3 device /dev/da3e > drive d4 device /dev/da4e > drive d5 device /dev/da5e > drive d6 device /dev/da6e > drive d7 device /dev/da7e > drive d8 device /dev/da8e > drive d9 device /dev/da9e > # Our volume with two striped plexes, slightly different in size > volume data1 plex p1 > plex name p1 org striped 512k > sd name sd2 length 17836403b drive d2 > sd name sd3 length 17836403b drive d3 > sd name sd5 length 17836403b drive d5 > sd name sd6 length 17836403b drive d6 > volume data2 plex p2 > plex name p2 org striped 512k > sd name sd4 length 17782939b drive d4 > sd name sd7 length 17782939b drive d7 > sd name sd8 length 17782939b drive d8 > sd name sd9 length 17782939b drive d9 You haven't said what happens. It would be nice to see the output of `vinum create -V /etc/vinum.cf'. > Things are badly screwed up enough that I can't figure out how to > delete any of the previous runs, and I can't figure out how to correct > any of the existing data. I keep doing a "vinum resetconfig" and then > "sync;sync;sync;shutdown -r now" in order to avoid the kernel panic > problem that I reported previously. And what happens? There were a couple of gross uglinesses in the resetconfig and unload code which occasionally caused hangs or panics. I've fixed them in -CURRENT, but not yet in -STABLE. You'd probably be better off using the -CURRENT version of Vinum (it's still, as of today, fully compatible with -STABLE). It shouldn't panic. If you (or anybody else) get a panic with Vinum, PLEASE REPORT IT. Vinum's a complicated driver to debug, and I can't hope to do all the testing myself. If you don't report a panic, it's probably going to happen again. There are detailed instructions on what to do in vinum(4). Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990313090046.F429>