Why systemd.mountd does not always activate Volume groups(VGs) during server reboot?

Solution In Progress - Updated -

Issue

  • Server boots intermittently into emergency mode, having a minimal subset of the filesystems mounted each reboot
  • system halt at boot time
  • Packages installed for device-mapper and lvm2
device-mapper-1.02.107-5.el7.x86_64
device-mapper-event-1.02.107-5.el7.x86_64
device-mapper-event-libs-1.02.107-5.el7.x86_64
device-mapper-libs-1.02.107-5.el7.x86_64
device-mapper-persistent-data-0.5.5-1.el7.x86_64
========
lvm2-2.02.130-5.el7.x86_64
lvm2-libs-2.02.130-5.el7.x86_64
  • We can not upgrade to 7.3 because our veritas product is not compatible 7.3 for the moment
# grep -i lvmetad /etc/lvm/lvm.conf
# If lvmetad is used, then see "A note about device filtering while
    # lvmetad is used" comment that is attached to global/use_lvmetad setting.
    use_lvmetad = 0
  • pvscan --cache already run but issue is still there

Environment

  • Red Hat Enterprise Linux 7.1(RHEL)
  • Logical Volume Manager(lvm2)
  • Systemd

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.