From owner-freebsd-alpha  Fri Mar 16 17:38:37 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37])
	by hub.freebsd.org (Postfix) with ESMTP id 47DD537B71C
	for <freebsd-alpha@freebsd.org>; Fri, 16 Mar 2001 17:38:33 -0800 (PST)
	(envelope-from nospam@videotron.ca)
Received: from videotron.ca (client32.quantum.net [192.168.56.32])
	by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2H1caw26311
	for <freebsd-alpha@freebsd.org>; Fri, 16 Mar 2001 20:38:37 -0500 (EST)
Message-ID: <3AB2C01C.9080509@videotron.ca>
Date: Fri, 16 Mar 2001 20:38:36 -0500
From: tcn <nospam@videotron.ca>
Reply-To: leclercn@videotron.ca
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-alpha@freebsd.org
Subject: vinum & dhcp3 port problems
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

vinum)

  I am having difficulties with vinum.  I recently had to recreate my 
plexes so I resetted the configuration and started a fresh one.  I had a 
raid1 configuration.  Whenever I try to reate the mirror, vinum throws a 
segmentation fault "eg. mirror -n mirror /dev/da0g /dev/da2f".  When I 
set verbose on, I get a core dump (sig 11 - don't you say it's my 
hardware, I can reproduce this as often as I want and no other part of 
the system is having this behaviour).  I then tried to print the config 
and had another dump after seeing this line:  "drive ve0 device".  ve0 
should have been vinumdrive0.  I also found that ve0 and ve1 links are 
created in the current directory pointing into /dev/vinum/drive/veX.  
The vinum directory in /dev doesn't change at all.  No volume/plex/sd is 
created.  This looks like a bad pointer or something.

  Has vinum changed since 4.3-BETA20000308 ?


dhcp3 port)

   I tried this port and found that it cannot answer any queries.  I 
suspect an int size problem.  dhcp2 port works fine, dhcp3 drops bogus 
hlen packets.  (and there aren't any!)


Normand Leclerc
leclercn@videotron.ca


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message