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.
Description of problem:
When doing clustered mirror tests which involve snapshots, every once in a while the entries in /dev/vgname/ are not removed.
It could be due to some race
Version-Release number of selected component (if applicable):
3.10.0-121.el7.x86_64
lvm2-2.02.105-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
lvm2-libs-2.02.105-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
lvm2-cluster-2.02.105-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
device-mapper-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
device-mapper-libs-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
device-mapper-event-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
device-mapper-event-libs-1.02.84-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
device-mapper-persistent-data-0.3.2-1.el7 BUILT: Thu Apr 3 16:58:51 CEST 2014
cmirror-2.02.105-14.el7 BUILT: Wed Mar 26 14:29:41 CET 2014
How reproducible:
50% of the time.
Steps to Reproduce:
Was able to reproduce currently only on autmatic tests. They need to run for a while and the failure will occur for sure.
Actual results:
The LV was removed but the entry remained in the devfs:
[root@virt-062 mirror_sanity]# lvs
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
exclusive_origin mirror_sanity owi-a-m--- 100.00m exclusive_origin_mlog 100.00
msnap_2 mirror_sanity swi-a-s--- 20.00m exclusive_origin 0.00
msnap_3 mirror_sanity swi-a-s--- 20.00m exclusive_origin 0.00
msnap_4 mirror_sanity swi-a-s--- 20.00m exclusive_origin 0.00
msnap_5 mirror_sanity swi-a-s--- 20.00m exclusive_origin 0.00
root rhel_virt-062 -wi-ao---- 6.71g
swap rhel_virt-062 -wi-ao---- 820.00m
[root@virt-062 mirror_sanity]# dmsetup ls
mirror_sanity-msnap_2 (253:10)
mirror_sanity-msnap_3-cow (253:11)
mirror_sanity-msnap_4-cow (253:13)
mirror_sanity-exclusive_origin_mimage_1 (253:4)
mirror_sanity-msnap_5-cow (253:15)
mirror_sanity-exclusive_origin_mimage_0 (253:3)
rhel_virt--062-swap (253:1)
rhel_virt--062-root (253:0)
mirror_sanity-exclusive_origin_mlog (253:2)
mirror_sanity-msnap_5 (253:16)
mirror_sanity-exclusive_origin (253:5)
mirror_sanity-exclusive_origin-real (253:6)
mirror_sanity-msnap_4 (253:14)
mirror_sanity-msnap_2-cow (253:9)
mirror_sanity-msnap_3 (253:12)
[root@virt-062 mirror_sanity]# ls -l /dev/mirror_sanity/
total 0
lrwxrwxrwx. 1 root root 7 Apr 25 15:17 exclusive_origin -> ../dm-5
lrwxrwxrwx. 1 root root 7 Apr 25 15:17 exclusive_origin_mimage_0 -> ../dm-3
lrwxrwxrwx. 1 root root 7 Apr 25 15:17 exclusive_origin_mimage_1 -> ../dm-4
lrwxrwxrwx. 1 root root 7 Apr 25 15:17 exclusive_origin_mlog -> ../dm-2
lrwxrwxrwx. 1 root root 7 Apr 25 15:17 msnap_1 -> ../dm-6
lrwxrwxrwx. 1 root root 8 Apr 25 15:17 msnap_2 -> ../dm-10
lrwxrwxrwx. 1 root root 8 Apr 25 15:17 msnap_3 -> ../dm-12
lrwxrwxrwx. 1 root root 8 Apr 25 15:17 msnap_4 -> ../dm-14
lrwxrwxrwx. 1 root root 8 Apr 25 15:17 msnap_5 -> ../dm-16
As you can see in the last pasted block, the msnap_1 remained in /dev/mirror_sanity even though it is no longer present in LVM or dm.
Expected results:
Links related to the deleted LV should be removed as well.
Additional info:
I will try to find a manual reproducer, or at least a quick script which can run into this.
This behavior is currently preventing our tests from continuing after this point.
Created attachment 890400[details]
debug log of the last lvremove
I'm attaching a -vvvv debug log of the last lvremove, after which the devfs entries remain. Not sure if/how useful it is, but having some debug log is better than having none I suppose :)
Comment 3RHEL Program Management
2014-05-06 05:48:04 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
I suppose this is the same as bug #1119561, but I'll double check - in case the removal is properly propagated in cluster (which I expect it is via clvmd which then removes the mapping on each node), it is udev issue.
Yes, this is the same as bug #1119561, it doesn't need to be clustered even. Closing as dup.
*** This bug has been marked as a duplicate of bug 1119561 ***