From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 11 13:15:54 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 262C116A4CE; Sun, 11 Jan 2004 13:15:54 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6724F43D3F; Sun, 11 Jan 2004 13:15:52 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0BLFfET042294; Sun, 11 Jan 2004 14:15:42 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 11 Jan 2004 14:15:05 -0700 (MST) Message-Id: <20040111.141505.108953149.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <14092.1073845446@critter.freebsd.dk> References: <16385.37893.652979.822920@canoe.dclg.ca> <14092.1073845446@critter.freebsd.dk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: des@des.no cc: hackers@freebsd.org cc: current@freebsd.org cc: dgilbert@dclg.ca Subject: Re: Future of RAIDFrame X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2004 21:15:54 -0000 In message: <14092.1073845446@critter.freebsd.dk> "Poul-Henning Kamp" writes: : In message <16385.37893.652979.822920@canoe.dclg.ca>, David Gilbert writes: : >That said, we need a strong and robust software raid. : : And as long as we have something which "mostly work" there seems to : be insufficient motivation to make that happen. : : Therefore my proposal to send both RF and Vinum in training camp in p4. This has been a fundamental disagreement in the development model for a long time. Some people think this is a great idea, others hate it. The pros are that open source tends to be written best when there's pain and suffering to overcome. The cons are that sometimes things that are shot in the head never come back to life, leaving our users in the lurch. Maybe this would be a good test-case for seeing how well it works? Maybe not. We do need to run a few more test-cases for things through this scenario... I'm not sure this one is well suited to it. Warner