Date: Tue, 16 Feb 1999 15:00:17 +0100 From: Brad Knowles <blk@skynet.be> To: Greg Lehey <grog@lemis.com>, Philip Kizer <pckizer@nostrum.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Vinum questions? Message-ID: <19990216150017.004598@relay.skynet.be>
next in thread | raw e-mail | index | archive | help
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?
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
> 8: drive d5 device /dev/da5e
>** 8 Incorrect drive name d5 specified for drive drive5: Invalid argument
> 9: drive d6 device /dev/da6e
>** 9 Incorrect drive name d6 specified for drive drive6: Invalid argument
> 10: drive d7 device /dev/da7e
>** 10 Incorrect drive name d7 specified for drive drive7: Invalid argument
> 11: drive d8 device /dev/da8e
>** 11 Incorrect drive name d8 specified for drive drive8: Invalid argument
> 12: drive d9 device /dev/da9e
>** 12 Incorrect drive name d9 specified for drive drive9: Invalid argument
> 13: # Our volume with two striped plexes, slightly different in size
> 14: volume data1 plex p1
> 15: plex name p1 org striped 512k
> 16: sd name sd2 length 17836403b drive d2
> 17: sd name sd3 length 17836403b drive d3
> 18: sd name sd5 length 17836403b drive d5
>** 18 No space for sd5 on d5: No space left on device
> 19: sd name sd6 length 17836403b drive d6
>** 19 No space for sd6 on d6: No space left on device
> 20: volume data2 plex p2
> 21: plex name p2 org striped 512k
> 22: sd name sd4 length 17782939b drive d4
>** 22 No space for sd4 on d4: No space left on device
> 23: sd name sd7 length 17782939b drive d7
>** 23 No space for sd7 on d7: No space left on device
> 24: sd name sd8 length 17782939b drive d8
>** 24 No space for sd8 on d8: No space left on device
> 25: sd name sd9 length 17782939b drive d9
>** 25 No space for sd9 on d9: No space left on device
Then a kernel panic. 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):
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x1c
fault code = supervisor read, page not present
instruction pointer = 0x8:0xf11ba78a
stack pointer = 0x10:0xf9d79d60
frame pointer = 0x10:0xf9d79d98
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 205 (vinum)
interrupt mask =
trap number = 12
panic: page fault
syncing disks...
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.
--
These are my opinions -- not to be taken as official Skynet policy
____________________________________________________________________
|o| Brad Knowles, <blk@skynet.be> Belgacom Skynet NV/SA |o|
|o| Systems Architect, News/mail/FTP Admin Rue Col. Bourg, 124 |o|
|o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o|
|o| http://www.skynet.be Belgium |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Usenet is not the web. Just because the web handles some things
poorly is not a good reason to apply those same techniques to Usenet.
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?19990216150017.004598>