Why I got warning "WARNING: Disable lvmetad in lvm.conf. lvmetad should never be enabled in a clustered environment." from messages log ?

Solution Verified - Updated

Environment

  • Red Hat Enterprise Linux 7 with High Availability
  • lvm2-lvmetad.service

Issue

  • Why I got warning WARNING: Disable lvmetad in lvm.conf. lvmetad should never be enabled in a clustered environment. from /var/log/messages log?
  • After cluster failover, lvm size are not consistent between nodes.

Resolution

Before modifying the /etc/lvm/lvm.conf or stopping lvm2-lvmetad make sure that the cluster node does not have LVM resources enabled on it by either:

  • Putting the cluster node into standby.
  • Or moving all the LVM resources to another cluster node.

If you do procedure in the link below with LVM resources running on the node then it is possible for the resource to fail a monitor which could lead to one or more resources being stopped.

Then when there is no LVM resources running on the cluster node then use the following procedure to disable lvmetad: What is lvmetad and how do I disable it?

Root Cause

The lvmetad daemon process is not currently supported across the nodes of a cluster, and requires that the locking type be local file-based locking. This cause metadata of LVM to be out of sync with the other members of the cluster. Thelvmetad daemon process should never be running or enabled in a cluster environment.

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.