From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 24 02:01:23 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1C3716A4CE for ; Thu, 24 Jun 2004 02:01:23 +0000 (GMT) Received: from mail.ambrisko.com (adsl-64-174-51-43.dsl.snfc21.pacbell.net [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A31A43D48 for ; Thu, 24 Jun 2004 02:01:23 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) (192.168.1.2) by mail.ambrisko.com with ESMTP; 23 Jun 2004 19:01:18 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.9p2/8.12.9) with ESMTP id i5O21ISU048429; Wed, 23 Jun 2004 19:01:18 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.9p2/8.12.9/Submit) id i5O21H5g048428; Wed, 23 Jun 2004 19:01:17 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200406240201.i5O21H5g048428@ambrisko.com> In-Reply-To: <40D99D3B.8010608@DeepCore.dk> To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Date: Wed, 23 Jun 2004 19:01:17 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=unknown-8bit cc: freebsd-scsi@freebsd.org cc: Maxim Sobolev Subject: Re: HostRaid support on FreeBSD X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 02:01:24 -0000 Søren Schmidt writes: | Reading the metadata off the disks and using that info to access a RAID | array is easy and can be had even without docs in a few hours. Writing | back the metadata in case of failures etc to retain sanity of the array | is "somewhat" more difficult. Actually I'm working with this currently | for new formats for ata-raid and its not trivial to get right. Of which we've done the Intel 2 drive format read, write deal with broken mirrors etc. Writing and dealing with broke mirrors was harder and can lead to breaking the Intel RAID BIOS code :-( It's available in our -stable ata SATA patches that have been updated to 4.10-RELEASE. Doug A.