Description of problem: There has been a long standing discussion on the behavior of vgchange in a cluster in regard to exclusive activation of volumes. From the user/admin perspective it makes more sense to have the command unambiguously do what a user may expect, and not end up having random results sometimes. This has been reported a few times in bugs #677817 and later in #1191724 In the former it was at some point fixed to work as one would expect, but it is no longer the case even in RHEL6. So in short, we would benefit greatly of making vgchange more unambiguous by adding an option to LOCALLY activate LVs in a VG, in exclusive mode by supplying something like: vgchange -aley vg_name The command should return with an exit code of 1 (error out) if it cannot execute what the user demands due to some (or all) of LVs belonging to this VG being already active (or exclusively active) on another node. It should only return an exit code of 0 (success) if all LVs belonging to the VG in question are successfully locally activated.
When exclusive activation is requested - it's normally tried first locally - unless configuration (tags) routes activation to other node - local activation with exclusive lock happens. However - once the node is exclusively active - other nodes respect this exclusive lock. Currently lvm2 has no explicit support for exclusive & local activation - but as a workaround user could check after exclusive activation whether the LV is active locally.
*** Bug 1196585 has been marked as a duplicate of this bug. ***
I don't think this feature request makes sense in a future without 'clvmd'. closing WONTFIX.