Why does LVM/LVM-activate resource fails to stop when Commvault backup software is configured?

Solution Verified - Updated -


  • Even though Filesystem resource(s) is stopped (i.e. filesystem is unmounted), still the VG is unable to get deactivated.
  • Stop operation is failing on LVM resource after commvault snapshot backup.
  • When a relocation of the LVM or LVM-activate is triggered and the setup has Commvault backup software configured for the backup, the cluster resource fails to deactivate.
  • Command pcs resource move fail to deactivate the VG and fenced the node after Commvault snapshot backup:
lvm_stop_0 on node1.local 'error' (1): call=496, status='complete', exitreason=testvg: failed to deactivate.'


  • Red Hat Enterprise Linux 7, 8 or 9
  • Pacemaker Cluster
  • Commvault backup software with Snapshot level backup

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