On 07/24/2012 01:56 PM, Chris Boot wrote: >> I plug in to a port on card A, I see the LUNs. >> I plug in to a port on card B, I get nothing. >> >> Yes? > > I wish that were the case, but no. The FireWire stack in Linux has no > way to only expose a unit on one fw_card - you get your unit on all the > config directories (all fw_cards) when you register it. The way I wrote > the SBP target, when you create a tport, the GUID that is the name of > the tport turns into the GUID in the SBP target's unit structure, and > has no connection with any specific fw_device. Now I understand why you were saying the tport GUID can be arbitrary. ISTR you talking about this when you were implementing sbp target, and I didn't get it then but didn't ask further. Thanks for the explanation. Not sure if this is a bug or a feature, but it *is* different than other target fabrics. :) The best way forward may be to just limit sbp fabric to a singleton target (with some dummy name), which will have the single tpg with the 1+ luns underneath, and accessible from all fw cards. Regards -- Andy -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
