From owner-freebsd-questions@FreeBSD.ORG Sat May 28 01:16:05 2005 Return-Path: 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 218CD16A41C for ; Sat, 28 May 2005 01:16:05 +0000 (GMT) (envelope-from FreeBSD@amadeus.demon.nl) Received: from post-22.mail.nl.demon.net (post-22.mail.nl.demon.net [194.159.73.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id C134743D48 for ; Sat, 28 May 2005 01:16:04 +0000 (GMT) (envelope-from FreeBSD@amadeus.demon.nl) Received: from amadeus.demon.nl ([82.161.18.200]:58434) by post-22.mail.nl.demon.net with esmtp (Exim 4.43) id 1Dbpvn-000PKj-K1; Sat, 28 May 2005 01:16:03 +0000 In-Reply-To: <6.2.1.2.0.20050527103652.05d9b538@imap.telissant.com> References: <6.2.1.2.0.20050527101153.05fd37b0@imap.telissant.com> <74B17732-6E54-4C34-B899-201DA91F5B91@amadeus.demon.nl> <6.2.1.2.0.20050527103652.05d9b538@imap.telissant.com> Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <8F645B9F-365A-4D82-896E-69A9ADDB7EB8@amadeus.demon.nl> Content-Transfer-Encoding: 7bit From: FreeBSD questions mailing list Date: Sat, 28 May 2005 03:16:02 +0200 To: web@3dresearch.com X-Mailer: Apple Mail (2.730) Cc: freebsd 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2005 01:16:05 -0000 On 27 mei 2005, at 16:38, web@3dresearch.com wrote: > > >>> [...] >>> >>> 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 >> > > Many thanx... I guess I better stick with 4.11 > > jd > > you're welcome maybe the complete vinum chapter should be removed from the handbook? Arno