Why 'vgs' failed with SIGBUS error?

Solution Verified - Updated -

Issue

  • LVM command segfaulting within PCS cluster.
  • Cluster resource crashed and LVM command segfault with SIGBUS error
Aug 24 18:40:59 node2 abrt-hook-ccpp[97280]: Process 97278 (lvm) of user 0 killed by SIGBUS - dumping core
Aug 24 18:40:59 node2 LVM(ora_shared1_vg)[97238]: ERROR: WARNING: Ora_Shared1_vg is active without the cluster tag, "pacemaker"
Aug 24 18:40:59 node2 lrmd[71951]:   notice: ora_shared1_vg_monitor_10000:97238:stderr [ ocf-exit-reason:WARNING: Ora_Shared1_vg is active without the cluster tag, "pacemaker" ]
Aug 24 18:40:59 node2 crmd[71954]:   notice: node2.dba.cdom-ora_shared1_vg_monitor_10000:103 [ ocf-exit-reason:WARNING: Ora_Shared1_vg is active without the cluster tag, "pacemaker"\n ]
Aug 24 18:40:59 node2 lrmd[71951]:   notice: ora_shared2_vg_monitor_10000:97245:stderr [   /etc/lvm/cache/.cache.tmp: rename to /etc/lvm/cache/.cache failed: No such file or directory ]
Aug 24 18:41:00 node2 abrt-server[97302]: Duplicate: core backtrace
Aug 24 18:41:00 node2 abrt-server[97302]: DUP_OF_DIR: /var/spool/abrt/ccpp-2020-08-17-17:10:32-195031

Environment

  • Red Hat Enterprise Linux (RHEL) 7 with the High Availability Add-On
  • RHEL6 to 7 in-place upgrade

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In