Date: Fri, 18 Nov 2005 11:51:11 +0100 (CET) From: Lukas Ertl <le@FreeBSD.org> To: Scott Long <scottl@samsco.org> Cc: John Polstra <jdp@FreeBSD.org>, cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/cam/scsi scsi_cd.c scsi_da.c src/sys/geom geom_disk.c geom_disk.h geom_subr.c Message-ID: <20051118115031.D730@pcle2.cc.univie.ac.at> In-Reply-To: <437D94EA.90909@samsco.org> References: <200511180243.jAI2hnhJ050562@repoman.freebsd.org> <Pine.WNT.4.64.0511180943300.1072@korben> <437D94EA.90909@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Nov 2005, Scott Long wrote: > What does this mean for other drivers? RAID arrays can come and go > at runtime, either due to drive failure or due to actions by the user > via a management app. I don't recall ever seeing a problem like this > with the aac driver and creating/destroying arrays in a loop at runtime. I don't know about other drivers, but I've seen the exact problem on HP SmartArrays (ciss). cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051118115031.D730>