From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 30 00:51:45 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 CB3C316A4CE for ; Wed, 30 Jun 2004 00:51:45 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C45E43D53 for ; Wed, 30 Jun 2004 00:51:45 +0000 (GMT) (envelope-from bob@immure.com) Received: from maul.immure.com (adsl-66-136-206-1.dsl.austtx.swbell.net [66.136.206.1])i5U0pWX2016664; Tue, 29 Jun 2004 20:51:32 -0400 Received: (from root@localhost) by maul.immure.com (8.12.11/8.12.11) id i5U0pWRt002917; Tue, 29 Jun 2004 19:51:32 -0500 (CDT) (envelope-from bob@immure.com) Received: from luke.immure.com (luke.immure.com [10.1.132.3]) by maul.immure.com (8.12.11/8.12.3) with ESMTP id i5U0pVjX002881; Tue, 29 Jun 2004 19:51:31 -0500 (CDT) (envelope-from bob@immure.com) Received: from luke.immure.com (localhost [127.0.0.1]) by luke.immure.com (8.12.11/8.12.11) with ESMTP id i5U0pVbs080012; Tue, 29 Jun 2004 19:51:31 -0500 (CDT) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.12.11/8.12.11/Submit) id i5U0pVwG080011; Tue, 29 Jun 2004 19:51:31 -0500 (CDT) (envelope-from bob) Date: Tue, 29 Jun 2004 19:51:31 -0500 From: Bob Willcox To: "Kenneth D. Merry" Message-ID: <20040630005131.GA79967@luke.immure.com> References: <20040629200454.GF70022@luke.immure.com> <022301c45e34$124700d0$0b936f80@net.isber.ucsb.edu> <20040630001830.GA79686@luke.immure.com> <20040630004653.GA20146@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040630004653.GA20146@panzer.kdm.org> User-Agent: Mutt/1.5.6i X-scanner: scanned by Inflex 1.0.12.3 on maul.immure.com cc: freebsd-scsi@freebsd.org cc: randall ehren Subject: Re: Recommended RAID controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bob Willcox List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2004 00:51:46 -0000 On Tue, Jun 29, 2004 at 06:46:53PM -0600, Kenneth D. Merry wrote: > On Tue, Jun 29, 2004 at 19:18:30 -0500, Bob Willcox wrote: > > On Tue, Jun 29, 2004 at 04:52:01PM -0700, randall ehren wrote: > > > > > on a side note, does anyone know if it's possible to initiate a RAID > > > rebuild > > > > > using these utilities? they seem to only allow the viewing or status, > > > but > > > > > not initiate any changes... > > > > > > > > I thougth that the rebuild would be initiated automatically when you > > > > plug in the new drive. Is that not so? > > > > > > nope. put a new drive in, can't reboot the machine until this weekend, been > > > like this for about 36 hours now... > > > > Bummer. Seems like that ought to be automatic. > > Well, if you're writing the RAID controller firmware, you'll often want > some user intervention prior to treating a newly inserted drive as a spare. > > What if the user accidentally plugged the drive into the wrong SCSI (or > SATA or FC or ATA) bus? > > What if the user just wanted to treat the new drive as a volume, and put it > on the controller so he could access it? > > What if you have 2 (or more) failed arrays, how do you decide which array > gets the spare? > > You get the idea. You want to ask the user before potentially overwriting > his data. There are probably some RAID boxes that do treat newly inserted > drives as spares immediately, but you pretty much need some sort of > standing policy on what to do with a "foreign" drive in that case. Hmm, all good points. Guess I was thinking about this from the standpoint of simple convenience and overlooking the risks. :-) Bob > > Ken > -- > Kenneth Merry > ken@kdm.org -- Bob Willcox Serocki's Stricture: bob@immure.com Marriage is always a bachelor's last option. Austin, TX