Date: Wed, 17 Mar 1999 08:56:47 +1030 From: Greg Lehey <grog@lemis.com> To: Brad Knowles <blk@skynet.be>, Philip Kizer <pckizer@nostrum.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Vinum questions? Message-ID: <19990317085647.X429@lemis.com> In-Reply-To: <19990216150017.004598@relay.skynet.be>; from Brad Knowles on Tue, Feb 16, 1999 at 03:00:17PM %2B0100 References: <19990216150017.004598@relay.skynet.be>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 16 February 1999 at 15:00:17 +0100, Brad Knowles wrote: > On Tue, Mar 16, 1999, Greg Lehey <grog@lemis.com> wrote: > >>> mercury# vinum create -V /etc/vinum.conf >>> Mar 15 15:13:02 mercury /kernel: vinum: loaded >>> Mar 15 15:13:02 mercury /kernel: vinum: loaded >>> Can't get vinum config: Invalid argument >> >> You've gone and removed -DVINUMDEBUG somewhere, haven't you? There >> was a warning in vinum(4), but it's possibly confusing. I've changed >> it to: > > Okay, I downloaded 4.0-CURRENT, extracted the tarball, did a > make in /usr/src/sys/modules/vinum and then a make install (ensuring > that VINUMDEBUG was turned on). Went and modified the kernel in > /usr/src/sys/i386/config/ to include VINUMDEBUG, did a > /usr/sbin/config MERCURY, did the make depend, make, make install, > then sync;sync;sync;shutdown -r now. I've done this enough times > that this is almost a rote process for me, but I didn't miss > anything, did I? Yes. First, you configured it in the kernel, though I continually ask you not to, and secondly you forgot a resetconfig, since you changed the names of the drives. > After coming back up (but not yet having made any changes to the > previously posted /etc/vinum.conf file), I got: > >> mercury# vinum create -V /etc/vinum.conf >> 1: # /etc/vinum.conf - config file for vinum(8) >> 2: # >> 3: # Our drives >> 4: drive d1 device /dev/da1e >> 5: drive d2 device /dev/da2e >> 6: drive d3 device /dev/da3e >> 7: drive d4 device /dev/da4e >> ** 7 Incorrect drive name d4 specified for drive drive4: Invalid argument You've changed the names of the drives, but they're still stored on the drive. You need to do a resetconfig. > Then a kernel panic. When? Immediately after the create command? > I'm waiting for the machine to sync it's disks, but I'll type in as > much of the error as I can before it completes (please excuse any > typos): This isn't much use without a dump; we don't know what those addresses represent. If you can't get a dump, we'll have to do some looking through the kernel namelist to establish what they were. > Well, I got that easily done before it completed, so I'm guessing > that the sync wasn't successful, and that I probably won't have a > recoverable crash dump. Big Red Button time.... Well, it took a long > time to fsck /, but the machine appears to be up again. Let's see if we > can go find a crash dump.... Nope -- dumpdev hadn't been specified in > /etc/rc.conf. Let's do `dumpon -v /dev/da0s1b`, then try again. Fine. I suppose we can take this one offline. 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-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990317085647.X429>