When active logical volumes exist in a volume group that is being switched from non-clustered to clustered, the user may be unable to deactivate the logical volume. This issue can be avoided in a number of ways:
1) deactivate a volume group's logical volumes before changing its cluster status
2) activate the volume group cluster-wide after switching its status to 'clustered' (e.g. 'vgchange -ay <VG_name>')
3) re-activate the volume group locally after switching its
status to 'clustered' (e.g. 'vgchange -aly <VG_name>')
Any of the above three work-arounds is sufficient to enable the user to deactivate logical volume. #2 is the most obvious choice and most users will do this as a matter of course, since the objective is to allow multiple machines in a cluster to access the logical volumes.