> On 03/17/2014 11:11 PM, Jeremy Linton wrote: > > > > I didn't study the whole code path but does the VPD data get > > updated on a 6/2900? I suspect it should be. I can imagine a > > number of cases where the luns changed check condition gets > > preempted/lost by a device reset. I guess much of that should > > be masked by the port login/logout, but its probably better to > > be safe... > > See the unit attention condition precedence level table in the SCSI Architecture Model (sam5r15 table 54 page 121). POWER ON, RESET, OR BUS DEVICE RESET OCCURRED (29h 00h) has the highest precedence, meaning that any other unit attention condition might also have occurred but no longer be individually reported. Similarly, all the others in table 54 have precedence over (and thus imply the possibility of) INQUIRY DATA HAS CHANGED. In addition to the codes in table 54, since INQUIRY DATA HAS CHANGED has a nonzero ASCQ (3Fh 03h), it also has lower precedence than 3Fh 00h TARGET OPERATING CONDITIONS HAVE CHANGED. For generic SCSI code, the "protocol specific" codes may be the hardest to handle. That covers these old parallel SCSI codes: 29h 05h TRANSCEIVER MODE CHANGED TO SINGLE-ENDED 29h 06h TRANSCEIVER MODE CHANGED TO LVD but allows newer protocols to add codes if needed. You may need the LLD to report an optional list of extra codes to consider at that precedence level. -- 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
