A missing physical volume from a local volume group or vgexported volume groups causes an error that prevents clvm pacemaker resource from starting

Solution Unverified - Updated -

Issue

  • A missing physical volume from a local volume group causes an error that prevents the pacemaker resource clvm from starting.

    Sep 10 10:00:01 node1 clvmd: Cluster LVM daemon started - connected to Corosync
Sep 10 10:00:01 node1 clvm(clvmd)[18211]: ERROR:  1 logical volume(s) in volume group "cluster_vg2" now active Couldn't find device with uuid oZ9Aqw-SFcp-q4eK-zM3q-Xs8R-sEr2-Hntqg9. 
Error locking on node 1: Refusing activation of partial LV broken_vg/lvol1. Use '--activationmode partial' to override. 0 logical volume(s) in volume group "broken_vg" now active 1 logical volume(s) in volume group "cluster_vg1" now active 2 logical volume(s) in volume group "rootvg" now active
Sep 10 10:00:01 node1 clvm(clvmd)[18211]: INFO: Failed to activate VG(s):

  • A vgexported volume groups causes an error that prevents the pacemaker resource clvm from starting.

    Sep 10 10:00:01 node1 clvmd: Cluster LVM daemon started - connected to Corosync
Sep 10 10:00:01 node1 clvm(clvmd)[6118]: ERROR:  1 logical volume(s) in volume group "cluster_vg2" now active 1 logical volume(s) in volume group "cluster_vg1" now active Volume group "exportvg" is exported 2 logical volume(s) in volume group "rootvg" now active
Sep 10 10:00:01 node1 clvm(clvmd)[6118]: INFO: Failed to activate VG(s):

Environment

  • Red Hat Enterprise Linux Server 7 (with the High Availability Add On)
  • pacemaker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content