From owner-freebsd-questions@FreeBSD.ORG  Fri May 27 14:23:32 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AE8DF16A41C
	for <freebsd-questions@freebsd.org>;
	Fri, 27 May 2005 14:23:32 +0000 (GMT)
	(envelope-from FreeBSD@amadeus.demon.nl)
Received: from post-23.mail.nl.demon.net (post-23.mail.nl.demon.net
	[194.159.73.193])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5D8D243D1F
	for <freebsd-questions@freebsd.org>;
	Fri, 27 May 2005 14:23:32 +0000 (GMT)
	(envelope-from FreeBSD@amadeus.demon.nl)
Received: from amadeus.demon.nl ([82.161.18.200]:57876)
	by post-23.mail.nl.demon.net with esmtp (Exim 4.43)
	id 1DbfkJ-0006E9-7A; Fri, 27 May 2005 14:23:31 +0000
In-Reply-To: <6.2.1.2.0.20050527101153.05fd37b0@imap.telissant.com>
References: <F1siqXKx.1117141831.8494430.janos@imap.3dresearch.com>
	<E7568E07-D0E9-40D6-8558-76134712D0E6@amadeus.demon.nl>
	<6.2.1.2.0.20050527101153.05fd37b0@imap.telissant.com>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <74B17732-6E54-4C34-B899-201DA91F5B91@amadeus.demon.nl>
Content-Transfer-Encoding: 7bit
From: FreeBSD questions mailing list <FreeBSD@amadeus.demon.nl>
Date: Fri, 27 May 2005 16:23:30 +0200
To: jd <web@3dresearch.com>
X-Mailer: Apple Mail (2.730)
Cc: freebsd <freebsd-questions@freebsd.org>
Subject: Re: vinum: Inappropriate ioctl for device
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2005 14:23:32 -0000


On 27 mei 2005, at 16:13, web@3dresearch.com wrote:

>
>
>>> [...]
>>>
>>
>>
>>> Go back to 4.11!
>>> vinum is a nightmare in 5.4
>>> and gvinum is not nearly mature enough...
>>>
>>> I do have it running but every update it takes me 2 days to get the
>>> RAIDs back up
>>>
>>> Arno
>>>
>
> Arno,
>
> not very encouraging... Is it a RAID 5 you were able to make work  
> under 5.4?
>
> jd
>
>
hey
yeah a 3x160 GB RAID5 and 2x80 GB RAID 1 in FreeBSD 5.4-p1
  i get the same error message everytime i start vinum or whenever i  
execute a command in vinum
and really loads of kernel panics whenever i try to get it to work  
after a crash
i have an unorthodox way of recovering from this because it's nearly  
impossible to do stuff in vinum without causing kernel panics
yesterday evrything was ruined again (after upgrading to p1)
i wiped the complete config (rest config - NO FUTURE)
read in the config file (create RAID5)
set every state up manually (setstate up ...)
and rebuild parity
took about 10 hours to rebuild but then everything is back up and  
running

i tried Gvinum too but that doesn't have the setstate nor the ruibld  
parity command and still you can't stop gvinum (gvinum stop doesn't  
work, nor does kldunload geom_vinum.ko)

i have no way of changing to a different soft raid due to lack of  
space to backup so i'm stuck with this for as lo0ng as it takes :)

so, one advice "don't do it"
hehehe
Arno