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.

Bug 1112137

Summary:	Concurrent activations of same LV race against each other with "Device or resource busy"
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Kurik <jkurik>
Component:	lvm2	Assignee:	Alasdair Kergon <agk>
lvm2 sub component:	Activating existing Logical Volumes (RHEL6)	QA Contact:	Cluster QE <mspqa-list>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	agk, amureini, bazulay, cmarthal, coughlan, cpelland, dron, dwysocha, heinzm, iheim, jbrassow, jkt, jkurik, lpeer, lvm-team, mjuricek, msnitzer, nobody, nsoffer, pm-eus, prajnoha, prockai, scohen, thornber, yeylon, zkabelac
Version:	6.4	Keywords:	ZStream
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	lvm2-2.02.100-9.el6_5	Doc Type:	Bug Fix
Doc Text:	Concurrent activation and deactivation of logical volumes is now prohibited. Locking is performed so that operations are now processed sequentially. This does not apply to thin or cache logical volumes, nor in clusters. 'lvchange -ay $lv' and 'lvchange -an $lv' should no longer cause trouble if issued concurrently: the new lock should make sure they activate/deactivate $lv one-after-the-other, instead of overlapping.	Story Points:	---
Clone Of:	878948
Clones:	1127117 (view as bug list)		Environment:
Last Closed:	2014-11-26 09:36:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	878948
Bug Blocks:	1127117

Description Jan Kurik 2014-06-23 08:21:55 UTC

This bug has been copied from bug #878948 and has been proposed
to be backported to 6.5 z-stream (EUS).

Comment 6 Alasdair Kergon 2014-08-05 21:07:54 UTC

Primary bug is now VERIFIED so we shall proceed with this backport.

Comment 7 Alasdair Kergon 2014-08-05 21:09:22 UTC

Upstream patches:


https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=c1c2e838e88c56ef38d590007ca3b588ca06f1fd

https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=78533f72d30f6e840f66e0aae89126ef139c1f2c

Comment 8 Alasdair Kergon 2014-08-05 23:30:09 UTC

The change depended on some changes to the signal handling code, and rather than trying to work out how to separate this and perhaps introducing new bugs, in my first attempt at a backport, I have included these changes in full.

Comment 16 errata-xmlrpc 2014-11-26 09:36:37 UTC

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.

https://rhn.redhat.com/errata/RHBA-2014-1908.html