Just some thoughts Mike Christie wrote:
This is actually by design. Problem here is the port group as returned by REPORT TARGET PORT GROUPS does not have any association to the controller which handles these ports.
So I agree the hw handler just knows that it has paths unless you do something like chandra and send commands to figure out the contoller mappings. But are you saying that in userspace during dm mpath device setup time, there is no way to figure out the mappings? We talked about making the controller mappings and handling the problem where you cannot flood the box and the problem of having to send multiple commands more generic. We did not do that for rdac at the time because we thought scsi hw handlers were going to be done sooner, and did not want to redo the effort, but if it helps it could be done.
- 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
