Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug was initially created as a copy of Bug #1706154
I am copying this bug because:
This issue is also present on a RHEL8 system. The changes applied to fix 1706154 will be adapted and applied to RHEL8.
Description of problem:
LVM metadata and dmeventd stop jobs fail at reboot on VDO backed VG/LV
Version-Release number of selected component (if applicable):
vdo-6.1.1.125-3.el7.x86_64
kmod-kvdo-6.1.1.125-5.el7.x86_64
kernel-3.10.0-957.12.1.el7.x86_64
device-mapper-1.02.149-10.el7_6.7.x86_64
lvm2-2.02.180-10.el7_6.7.x86_64
Steps to Reproduce:
# vdo create --name=vdo1 --device=/dev/sda --vdoLogicalSize=12G
# vgcreate test /dev/mapper/vdo1
# lvcreate -n lv1 -l 50%FREE test
[root@localhost ~]# grep -r 'use_lvmetad =' /etc/lvm/lvm.conf
use_lvmetad = 1
[root@localhost ~]# grep test /etc/fstab
/dev/test/lv1 /lv1 xfs defaults,x-systemd.requires=vdo.service 0 0
[root@localhost ~]# grep lv1 /proc/mounts
/dev/mapper/test-lv1 /lv1 xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0
Reboot to test
Actual results:
When issuing reboot, the system does not shut down cleanly. It instead hangs on 2 stop jobs, lvm metadata daemon and dmeventd.
Expected results:
System should shut down cleanly.
Additional info:
Screenshots attached.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (kmod-kvdo bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4551