LVMLockFailedResize

If the lvextend or the lvresize command failes on cluster with

locking on node failed: resource temporarily unavailable

first, check the state of the logical volume. It may happened that the volume group in which the volume resides was made cluster-aware on a running cluster. In that case, all the volumes will be activated exclusively on the particular node. Type:

lvs -o lv_name,lv_active_exclusively <VG>

If some volumes are exclusively activated, we must deactivate all non-opened volumes on each of the cluster nodes and then re-ativate them.

bdbb