David Dillow, on 02/02/2011 07:44 PM wrote: > On Wed, 2011-02-02 at 15:27 -0500, Craig Prescott wrote: >> But if I add an additional target on the same target machine with, say: >> >> [root@hpcoss1 ~]# echo "add 7:0:1:0 3" >> >/proc/scsi_tgt/groups/Default/devices >> >> the srp_daemon on the initiator never sees the new storage and >> restarting srp_daemon doesn't seem to help. >> >> If I remove the SRP scsi devices, unload the ib_srp module, and reload >> it, I can see the new LUN (and I don't need to restart srp_daemon, >> either). But I don't think that is how it is supposed to work. > > Sounds about right for the existing code. There's no notification to the > initiator that you added a new LUN on an existing connection, so the LUN > will not show up on the client. There is a mechanism in the SCSI > standard for such things, but the Linux SCSI mid-layer does not > currently implement it.
I'm sorry, but I need to correct you. There is notification to the initiator that you added a new LUN on an existing connection. It is REPORT LUNS DATA HAVE CHANGED Unit Attention. SCST sends it. But it isn't processed anyhow on the initiator. Vlad -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
