Date: Fri, 18 Nov 2005 11:19:38 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Scott Long <scottl@samsco.org> Cc: John Polstra <jdp@FreeBSD.org>, cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Lukas Ertl <le@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: <7052.1132309178@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 18 Nov 2005 01:46:34 MST." <437D94EA.90909@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <437D94EA.90909@samsco.org>, Scott Long writes: >Lukas Ertl 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. Most drivers seem to detach their internal state from the struct disk, and therefore they don't need this. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7052.1132309178>