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.
A nested mutex lock could result in a deadlock in lvmetad, leading to a lockup (hang) in LVM commands trying to talk to lvmetad. The nested lock has been removed, avoiding the possibility of a deadlock.
Created attachment 663522[details]
gdb output
Description of problem:
deadlock in lvmetad
Version-Release number of selected component (if applicable):
lvm2-2.02.98-5.15.el6_4
How reproducible:
???
Steps to Reproduce:
1. ???
Actual results:
deadlock
Expected results:
pass
Additional info:
There were one `lvs -a -o +devices` and few `/sbin/lvm pvscan --cache --activate ay --major %d --minor %d` commands spawned by udev.
I have (hopefully) fixed the bug in fae1a611d2f907aa23c237b9f84df5089d30f728. A related fix is in 5294a6f77a900493b3e81eb70c1698ec3c4814b8. I would suggest both to be included in 6.4. No special QA treatment is required (the bug is exposed by existing testcases, it just triggers rarely).
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0501.html
Created attachment 663522 [details] gdb output Description of problem: deadlock in lvmetad Version-Release number of selected component (if applicable): lvm2-2.02.98-5.15.el6_4 How reproducible: ??? Steps to Reproduce: 1. ??? Actual results: deadlock Expected results: pass Additional info: There were one `lvs -a -o +devices` and few `/sbin/lvm pvscan --cache --activate ay --major %d --minor %d` commands spawned by udev.