Comment 7 for bug 1752115

You're correct about the shared-targets flag, however that was specifically to solve for locking create/delete of targets on backends using shared-targets. That's actually a different problem, it means that a single backend has multiple volumes that are all doing data transfer across a single 'shared' target.

In other words it has a different meaning here. We could possibly abuse that flag and use it to solve this problem, but there are a few things that would fall apart if we did that. Given the proposed solution works and I don't see any major drawbacks I would like to stick to the plan so to speak here.