Date: Fri, 18 Nov 2005 01:46:34 -0700 From: Scott Long <scottl@samsco.org> To: John Polstra <jdp@FreeBSD.org> Cc: 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: <437D94EA.90909@samsco.org> In-Reply-To: <Pine.WNT.4.64.0511180943300.1072@korben> References: <200511180243.jAI2hnhJ050562@repoman.freebsd.org> <Pine.WNT.4.64.0511180943300.1072@korben>
next in thread | previous in thread | raw e-mail | index | archive | help
Lukas Ertl wrote: > On Fri, 18 Nov 2005, John Polstra wrote: > >> jdp 2005-11-18 02:43:49 UTC >> >> FreeBSD src repository >> >> Modified files: >> sys/cam/scsi scsi_cd.c scsi_da.c >> sys/geom geom_disk.c geom_disk.h geom_subr.c >> Log: >> Fix a bug that caused some /dev entries to continue to exist after >> the underlying drive had been hot-unplugged from the system. Here > > > Thanks! > > cheers, > le > 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. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?437D94EA.90909>