In the cluster many volume types support only exclusive activation (snapshot, thins...). lmv2 tool has been automatically converting then any non-exclusive activation into 'exclusive' activation.
Such conversion however is not always correct. When a user has requested local activation, volume could have been activated exclusively on a different node in cluster.
Local activation is properly converted into local-exclusive activation.
When the local activation is successful the volume is locally and exclusively active.