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 644752 - pvs command takes p_global lock and serializes other (even unrelated) pvs commands
Summary: pvs command takes p_global lock and serializes other (even unrelated) pvs com...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Petr Rockai
QA Contact: Corey Marthaler
URL:
Whiteboard: storage
Depends On:
Blocks: 756082 773650 773651 773665 773677 773696 888457
TreeView+ depends on / blocked
 
Reported: 2010-10-20 08:07 UTC by Ayal Baron
Modified: 2013-06-17 15:22 UTC (History)
12 users (show)

Fixed In Version: lvm2-2.02.98-5.el6
Doc Type: Bug Fix
Doc Text:
Allow more than one process to iterate through Physical Volumes concurrently only when using lvmetad. lvmetad makes the existing lock unnecessary.
Clone Of:
Environment:
Last Closed: 2013-02-21 08:02:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0501 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2013-02-20 21:30:45 UTC

Description Ayal Baron 2010-10-20 08:07:15 UTC 
Description of problem:
Running "pvs" takes an exclusive lock which prevents running multiple pvs commands concurrently.
Even if different filters are used (which contain entirely different devices) the commands are still serialized.
Comment 1 Alasdair Kergon 2010-10-28 11:44:19 UTC 
What is the full 'pvs' command line you are using?  (Perhaps an alternative command would suffice, or perhaps that specific form of the command doesn't need the lock even though it takes it by default.)
Comment 2 Ayal Baron 2010-10-28 12:07:48 UTC 
pvs --config (filter with one device) PV_NAME
with or without additional fields, but I don't think that should matter.
Comment 3 Alasdair Kergon 2010-10-28 12:34:00 UTC 
which fields?  pv fields?  vg fields?  lv fields?  It makes a difference.
Comment 4 Alasdair Kergon 2010-10-28 12:35:23 UTC 
And do you know anything about the PV in advance?

For example, do you know that it always belongs to a VG - or might it be orphaned?  If it belongs to a VG do you know the name of that VG already or not?
Comment 5 Ayal Baron 2010-10-28 12:57:04 UTC 
pv fields.
and many times we know the name of the vg, yes, but if this pv does not contain an mda...
Comment 6 Alasdair Kergon 2010-10-28 13:01:27 UTC 
If you're only accessing PV fields, it's irrelevant whether there's an mda or not.
Comment 7 Alasdair Kergon 2010-10-28 13:02:55 UTC 
well - please just provide the lists of fields so we can see if there's anything we can do.   The global lock is certainly required by pvs in the general case, but perhaps your specific case doesn't need it - I don't know.
Comment 8 Ayal Baron 2010-11-24 10:58:00 UTC 
what we run today is:

lvm pvs --noheadings --units b --nosuffix --separator | -o uuid,name,size,vg_name,vg_uuid,pe_count,pe_alloc_count,mda_count
Comment 10 Milan Broz 2011-03-23 11:53:27 UTC 
So it prints fields which need to be parsed from metadata (not only field in PV header).

This is basically either request for some unlocked way how to read metadata and/or for performance improvement when reading it.
Comment 17 Alasdair Kergon 2012-12-05 15:02:32 UTC 
So *if* lvmetad is in use, can we skip setting lock_global in process_each_pv() and rely on individual locks instead?
Comment 18 Petr Rockai 2012-12-06 11:03:17 UTC 
Hmm. I think it should be OK to not take the lock if we are talking to lvmetad, but we should double-check that no other code (besides just reading metadata) relying on the lock crept in.
Comment 20 Petr Rockai 2012-12-12 13:45:11 UTC 
Pushed upstream as e5709a3..b19f840.
Comment 22 Nenad Peric 2012-12-12 14:14:30 UTC 
Marking as SanityOnly, 
QA will mark it as verified upon completion of the last REG test run.
Comment 24 errata-xmlrpc 2013-02-21 08:02:54 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/RHBA-2013-0501.html
Note You need to log in before you can comment on or make changes to this bug.