Date: Mon, 15 Mar 1999 14:28:06 +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: <19990315142806.012614@relay.skynet.be> In-Reply-To: <19990313090046.F429@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 13, 1999, Greg Lehey <grog@lemis.com> wrote:
>You haven't said what happens. It would be nice to see the output of
>`vinum create -V /etc/vinum.cf'.
Okay, after grabbing and making the 14 Mar vinum-3.1-STABLE.tar.gz
version, I get (and it's pretty ugly):
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
1: # /etc/vinum.conf - config file for vinum(8)
2: #
3: # Our drives
4: drive d1 device /dev/da1e
Mar 15 15:13:02 mercury /kernel: vinumioctl: invalid ioctl from process
5899 (vinum): 40444641
Mar 15 15:13:02 mercury /kernel: vinumioctl: invalid ioctl from process
5899 (vinum): 40444641
5: drive d2 device /dev/da2e
6: drive d3 device /dev/da3e
Mar 15 15:13:02 mercury /kernel: vinum: drive d1 is up
Mar 15 15:13:02 mercury /kernel: vinum: drive d1 is up
7: drive d4 device /dev/da4e
Mar 15 15:13:02 mercury /kernel: vinum: drive d2 is up
Mar 15 15:13:02 mercury /kernel: vinum: drive d2 is up
** 7 Incorrect drive name d4 specified for drive drive4: Invalid argument
8: drive d5 device /dev/da5e
Mar 15 15:13:03 mercury /kernel: vinum: drive d3 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d3 is up
** 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
Mar 15 15:13:03 mercury /kernel: vinum: drive d4 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d4 is up
** 10 Incorrect drive name d7 specified for drive drive7: Invalid argument
11: drive d8 device /dev/da8e
Mar 15 15:13:03 mercury /kernel: vinum: drive d5 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d5 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d6 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d6 is up
** 11 Incorrect drive name d8 specified for drive drive8: Invalid argument
12: drive d9 device /dev/da9e
Mar 15 15:13:03 mercury /kernel: vinum: drive d7 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d7 is up
** 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
** 16 No space for sd2 on d2: No space left on device
17: sd name sd3 length 17836403b drive d3
** 17 No space for sd3 on d3: No space left on device
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
Can't save Vinum config: Invalid argument
Mar 15 15:13:03 mercury /kernel: vinum: drive d8 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d8 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d9 is up
Mar 15 15:13:03 mercury /kernel: vinum: drive d9 is up
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: data1 is up
Mar 15 15:13:03 mercury /kernel: vinum: data1 is up
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: sd5 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: sd5 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: sd6 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: sd6 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: sd4 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: sd4 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: p2 is faulty
Mar 15 15:13:03 mercury /kernel: vinum: p2 is faulty
Mar 15 15:13:03 mercury /kernel: vinum: data2 is up
Mar 15 15:13:03 mercury /kernel: vinum: data2 is up
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p2 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p2 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: sd7 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: sd7 is crashed
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:03 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: plex p2 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: plex p2 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: sd8 is crashed
Mar 15 15:13:04 mercury /kernel: vinum: sd8 is crashed
Mar 15 15:13:04 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Can't get vinum config: Invalid argument
Can't get vinum config: Invalid argument
mercury# Mar 15 15:13:04 mercury /kernel: vinum: plex p2 does not have at
least 2 subdisks
Mar 15 15:13:04 mercury /kernel: vinum: plex p2 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: sd9 is crashed
Mar 15 15:13:04 mercury /kernel: vinum: sd9 is crashed
Mar 15 15:13:04 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: plex p1 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: plex p2 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinum: plex p2 does not have at least 2
subdisks
Mar 15 15:13:04 mercury /kernel: vinumioctl: invalid ioctl from process
5899 (vinum): 80044648
Mar 15 15:13:04 mercury /kernel: vinumioctl: invalid ioctl from process
5899 (vinum): 80044648
Mar 15 15:13:04 mercury /kernel: vinumioctl: invalid ioctl from process
5899 (vinum): 40444641
Mar 15 15:13:04 mercury /kernel: vinumioctl: invalid ioctl from process
5899 (vinum): 40444641
mercury# Mar 15 15:13:04 mercury /kernel: vinumioctl: invalid ioctl from
process 5899 (vinum): 40444641
Mar 15 15:13:04 mercury /kernel: vinumioctl: invalid ioctl from process
5899 (vinum): 40444641
mercury#
>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.
You mean vinum-4.0-CURRENT.tar.gz? Does this require FreeBSD
4.0-CURRENT, or can this install on top of FreeBSD 3.1-STABLE? I've been
sticking with the -STABLE versions precisely because I didn't want to
deal with any code that wasn't quite ready for production use and had
therefore been put into -CURRENT, but not yet qualified for inclusion in
-STABLE.
I feel sufficiently comfortable with using -STABLE for production
servers, even though I don't have all that much experience with FreeBSD.
I do not yet feel competent to have a -CURRENT server in production, and
if that's my only option I may be forced to blow away the server yet once
again and try yet another OS.
>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).
Well, short of the kernel panic previously reported (and which I have
studiously avoided trying to duplicate ;-), the only problems I've run
into have been failures to configure in the manner in which I would
expect/desire, so I've been making various configuration changes in an
attempt to get things to work. And in between those configuration
changes, to make sure that there's no left over cruft from previous runs
that is confusing the issue, I have been wiping all configuration
information and rebooting the server in question.
--
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|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
The Sky is no longer the limit
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?19990315142806.012614>