James Bottomley <James.Bottomley@xxxxxxxxxxxx> wrote: > On Thu, 2006-04-13 at 13:35 -0500, Cameron, Steve wrote: > > If it's a bad idea for general usage... maybe some > > way to permit it on a per scsi host basis? Maybe a > > way to enable/disable this feature thru sysfs or > > something, with the default being disabled? > > > > Otherwise our SNMP agents won't be able to know that > > fans failed, overtemp etc. in the storage box. > > Erm, as I read the MSA30 documentation, it has fourteen drive bays. > That means it has 14 targets plus the processor, so since 16 is the > addressing capacity of a wide SPI bus, there doesn't seem to be a need > to have the initiator and the processor at the same ID ... what's the > reason they have to be? One could be leaving room for another initiator in a multi-initiator environment. To answer the previous question. Since single bit selection is not supported the peripheral bay can monitor the bus looking for this condition. Once it sees this state and tries to validate it with some timing it can assume that the the initiator wants to select the peripheral bay. It normally does not support disconnects as it is only sending back SES like data. -andmike -- Michael Anderson andmike@xxxxxxxxxx - : 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
