Bug 523441

Summary:	LVM commands take a VERY long time (>40 min) to finish
Product:	Red Hat Enterprise Linux 5	Reporter:	RHEL Program Management <pm-rhel>
Component:	lvm2	Assignee:	Milan Broz <mbroz>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	5.4	CC:	abaron, acathrow, agk, bmarzins, cmarthal, cpelland, cplisko, dshaks, dwilson, dwysocha, edamato, heinzm, iheim, jbrassow, mbroz, msnitzer, ovirt-maint, pcormier, pep, pm-eus, prockai, pvrabec, riek, rluxenbe, sfrank, ykaul
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-10-05 07:18:47 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:	515232
Bug Blocks:	518493

Description RHEL Program Management 2009-09-15 14:07:48 UTC

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

Comment 3 Milan Broz 2009-09-16 10:19:34 UTC

Patch in lvm2-2.02.46-8.el5_4.1.

Comment 6 errata-xmlrpc 2009-10-05 07:18:47 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1476.html

Comment 7 Ayal Baron 2009-10-15 16:36:29 UTC

what value should "prioritise_write_locks" be given?(In reply to comment #6)
> An advisory has been issued which should help the problem
> described in this bug report. This report is therefore being
> closed with a resolution of ERRATA. For more information
> on therefore solution and/or where to find the updated files,
> please follow the link below. You may reopen this bug report
> if the solution does not work for you.
> 
> http://rhn.redhat.com/errata/RHBA-2009-1476.html  

what value should "prioritise_write_locks = ?" be set to?

Comment 8 Milan Broz 2009-10-15 17:05:11 UTC

See comments directly in lvm.conf (0 - disable, 1 - enable):

    # Whenever there are competing read-only and read-write access requests for
    # a volume group's metadata, instead of always granting the read-only
    # requests immediately, delay them to allow the read-write requests to be
    # serviced.  Without this setting, write access may be stalled by a high
    # volume of read-only requests.
    # NB. This option only affects locking_type = 1 viz. local file-based
    # locking.
    prioritise_write_locks = 1

Comment 9 Alasdair Kergon 2009-10-15 17:52:26 UTC

It's enabled by default.  That option is there so that if unanticipated problems are discovered with the change it can be turned off without needing to revert the package update.