Date: Wed, 23 Jun 2004 16:11:54 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: Maxim Sobolev <sobomax@portaone.com> Cc: freebsd-current@freebsd.org Subject: Re: HostRaid support on FreeBSD Message-ID: <xzpoenanz2t.fsf@dwp.des.no> In-Reply-To: <40D95FDC.9060802@portaone.com> (Maxim Sobolev's message of "Wed, 23 Jun 2004 13:47:56 %2B0300") References: <5.2.1.1.0.20040621135534.068fef40@server01.chassis00.xsnetworks.net> <40D7E0B7.1000905@portaone.com> <40D8D217.5000808@freebsd.org> <40D95FDC.9060802@portaone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev <sobomax@portaone.com> writes: > Well, my knowelege about internals of software RAID controllers is > quite limited, but as long as I know they are no more than BIOS with > UI for setting up RAIDs and interface to main BIOS that hides internal > RAID structure allowing to boot off the RAID. Also they provide some > persistent storage for RAID configuration, I assume either in some > controller's NVRAM or on the HDDs. The configuration is always stored on-disk, otherwise it wouldn't be possible to recover from controller failure. > Therefore, the same set of GEOM > RAID modules can work with different software RAID controllers (SCSI, > ATA, SATA etc) if there will be a standard way to extract this info > from the controller's driver, and present it in some common > format. That's what I am talking about. You're kicking down open doors. This problem has already been solved for Vinum, which is conceptually identical from a GEOM point of view. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpoenanz2t.fsf>