Date: Tue, 16 Mar 1999 08:51:55 +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: <19990316085155.E429@lemis.com> In-Reply-To: <19990315142806.012614@relay.skynet.be>; from Brad Knowles on Mon, Mar 15, 1999 at 02:28:06PM %2B0100 References: <19990313090046.F429@lemis.com> <19990315142806.012614@relay.skynet.be>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 15 March 1999 at 14:28:06 +0100, Brad Knowles wrote:
> 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
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:
DEBUG OPTIONS
The current version of vinum, both the kernel module and the user program
vinum(8), include significant debugging support. It is not recommended
to remove this support at the moment, but if you do you must remove it
from both the kernel and the user components. To do this, edit the files
/usr/src/sbin/vinum/Makefile and /usr/src/sys/modules/vinum/Makefile and
edit the CFLAGS variable to remove the -DVINUMDEBUG option. If you have
configured vinum into the kernel, either specify the line
options VINUMDEBUG
in the kernel configuration file or remove the -DVINUMDEBUG option from
/usr/src/sbin/vinum/Makefile as described above.
If the VINUMDEBUG variables do not match, vinum(8) will fail with the
message
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
This is another indication of the debug mismatch. The remainder of
the output is a result of this problem.
>> 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?
Yes.
> Does this require FreeBSD 4.0-CURRENT, or can this install on top of
> FreeBSD 3.1-STABLE?
You can install it on top of 3.1-STABLE. The versions haven't
diverged that much yet.
> 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.
The difference at the moment is simply that I'm being cautious and
waiting for reports back before committing exactly the same changes to
-STABLE. If you're having trouble, though, it's better to take the
newest stuff.
Having said that, of course, your problem here is obvious. On the
other hand, I've recently fixed a number of obscure bugs in -CURRENT,
and I'll be committing them to -STABLE RSN.
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?19990316085155.E429>