Bug 692149

Summary: [vdsm] Volume operations can deadlock themselves
Product: Red Hat Enterprise Linux 6 Reporter: David Naori <dnaori>
Component: vdsmAssignee: Saggi Mizrahi <smizrahi>
Status: CLOSED ERRATA QA Contact: David Naori <dnaori>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1CC: abaron, bazulay, hateya, iheim, ilvovsky, mgoldboi, mkenneth, tdosek, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.9-74.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 07:09:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
full vdsm log none

Description David Naori 2011-03-30 14:38:14 UTC
Created attachment 488782 [details]
full vdsm log

Description of problem:
when 140 vms is running on a host, trying to add new SD fails - getStoragePoolInfo Stuck forever.

Version-Release number of selected component (if applicable):
vdsm-4.9-57.el6.x86_64
libvirt-0.8.7-15.el6.x86_64

Steps to Reproduce:
1.run 140 vms
2.try to add new storage domain.

*Full vdsm log attached

Comment 2 RHEL Program Management 2011-04-04 02:14:03 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Saggi Mizrahi 2011-06-01 12:27:17 UTC
http://gerrit.usersys.redhat.com/509

Comment 6 Tomas Dosek 2011-07-12 07:26:14 UTC
Verified - vdsm-4.9-79.el6 - above described scenarios no longer reproduce + different scenarios (mainly async tasks on overloaded environment + fail of storage, vdsm, etc.) don't reproduce the lock of storage operations.

Comment 7 errata-xmlrpc 2011-12-06 07:09:59 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.

http://rhn.redhat.com/errata/RHEA-2011-1782.html