Bug 1039772 – lvm commands blocking indefinitely

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1039772 - lvm commands blocking indefinitely

Summary:	lvm commands blocking indefinitely

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	lvm2-cluster (Show other bugs)
Sub Component:
Version:	5.9
Hardware:	All Linux

Priority	urgent Severity urgent
Target Milestone:	rc
Target Release:	---
Assigned To:	Peter Rajnoha
QA Contact:	Cluster QE
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	1005408
Blocks:
	Show dependency tree / graph

Reported:	2013-12-09 18:58 EST by Jan Kurik
Modified:	2014-01-13 10:15 EST (History)
CC List:	18 users (show)

See Also:
Fixed In Version:	lvm2-cluster-2.02.88-9.el5_10.2
Doc Type:	Bug Fix
Doc Text:	When one of the LVM client processes was killed, the clvmd daemon had to wait for a mutex to stop the LVM client thread. Consequently, lvm utility commands in a cluster became indefinitely blocked. This update introduces a patch which fixes the deadlock, and lvm utility commands now work correctly.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-01-13 10:15:41 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	476623	None	None	None	Never
Red Hat Product Errata	RHBA-2014:0021	normal	SHIPPED_LIVE	lvm2-cluster bug fix update	2014-01-13 15:13:44 EST

Groups: None (edit)

Description Jan Kurik 2013-12-09 18:58:05 EST

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

Comment 11 errata-xmlrpc 2014-01-13 10:15:41 EST

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-2014-0021.html

Note You need to log in before you can comment on or make changes to this bug.