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.

+++ This bug was initially created as a clone of Bug #916937 +++

Description of problem:
The LVM2 commands run by sos may hang acquiring locks if other LVM2 commands are running (and blocked) on the local machine or in a clustered LVM environment if locks are held by other nodes.

Since sos only issues read-only commands disable locking when calling these commands. 

Version-Release number of selected component (if applicable):
# rpm -q sos
sos-2.2-*

How reproducible:
100%

Steps to Reproduce:
1. Arrange for LVM2 locks to be held (e.g. SIGSTOP an lvm2 command while it holds locks or arrange for a cluster to be inquorate).
2. run sosreport
  
Actual results:
sosreport blocks running lvm2 commands

Expected results:
sosreport exits with success

Additional info:

commit 711f644b9c655c644fb4bfa27e1c9292e525c719
Author: Bryn M. Reeves <bmr>
Date:   Mon Jun 23 16:57:11 2014 +0100

    Set global{locking_type=0} when running lvm2 commands
    
    Backport of dd478c2.
    
    The lvm2 commands that sos issues are all read-only. Disable
    locking when running the commands to avoid blocking if another
    process or node is holding a lock.
    
    Signed-off-by: Bryn M. Reeves <bmr>

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-1528.html