On Thu, 2008-07-31 at 09:15 -0500, James Bottomley wrote: > Oh ... you're not really talking about hotplug, which is why everyone is > confused. Hotplug is when you add or remove something from the bus. > What you've done is reconfigure the array. > > Most of the hotplug we do depends on the transport model (because what's > on the transport is changing). Array reconfiguration has no hotplug > event because SAM-3 has no real way of passing the information > asynchronously. The best it can do is Unit Attention/reported luns data > has changed (asc=0x3f/ascq=0xe) on the next command. > > The problem is that there's no way to process the event correctly even > when we get it. All we can do is issue another report LUNS command and > compare. However, just because it looks like a single LUN disappeared > doesn't mean the others weren't permuted or altered in some way (which > data we cannot get). > Why? if I keep a mapping between sg devices and device id (Inquiry page 0x83) then I have all the data. Gal. > So ... this event is manual intervention required because you have to > tell SCSI what you did to the array, it can't work it out for itself. > > James > > -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
