From owner-freebsd-current Tue Sep 28 20:41:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (Postfix) with SMTP id 851081594C for ; Tue, 28 Sep 1999 20:41:45 -0700 (PDT) (envelope-from john.saunders@nlc.net.au) Received: (qmail 17187 invoked by uid 1000); 29 Sep 1999 13:41:42 +1000 Date: 29 Sep 1999 13:41:42 +1000 Message-ID: <19990929034142.17186.qmail@nhj.nlc.net.au> From: "John Saunders" To: "Rodney W. Grimes" Cc: freebsd-current@freebsd.org Subject: Re: System crash on "vinum start" X-Newsgroups: nlc.lists.freebsd-current In-Reply-To: <199909282231.PAA16484@gndrsh.dnsmgr.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.37 (i686)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In freebsd-current you wrote: >> Being in the hardware RAID business myself I cannot help asking: why do you >> want to loose the hardware RAID in favor of a software solution? Flexibility >> (just guessing) or price maybe? > Because DPT has screwed this customer over for the last time... I suspect that back porting the ida (Compaq SMART RAID) driver from -current to 3.x would be both quicker and cheaper that the software development you propose. At least that way you don't have to deal with DPT. Any software additions to support hot swap and auto-rebuild would need to interoperate with vinum. From my understanding, vinum will survive a failed disk and continue to run. However no mechanism is yet available to automatically rebuild a new disk. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 04-1822-3814 (Phone) | \_,--\_/ | NORTHLINK COMMUNICATIONS P/L - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message