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 864902 - _lvmActivationNS resource not unlocked for a volume when no space is left on domain
Summary: _lvmActivationNS resource not unlocked for a volume when no space is left on ...
Keywords:
Status: CLOSED DUPLICATE of bug 815359
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: All
OS: All
unspecified
high
Target Milestone: rc
: ---
Assignee: Ayal Baron
QA Contact: Haim
URL:
Whiteboard: infra, storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-10 11:17 UTC by Lee Yarwood
Modified: 2018-12-01 18:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-21 09:07:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lee Yarwood 2012-10-10 11:17:56 UTC 
Description of problem:

Thanks to RHEV-M BZ#864892 VDSM can encounter a situation where it is unable to create a temp volume to preform a merge of a RAW base snapshot and COW active volume. 

When tearing down the volumes used during this process the _lvmActivationNS resource for the COW volume is not unlocked causing all subsequent attempts to merge or use the volume to hang waiting on the resource becoming free again even though the controlling task has died.

For example in the vdsm.log.1 file attached we can see the _lvmActivationNS resource for active COW volume being granted for the first merge task. 

# grep -rin '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498' vdsm.log.1
59091:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 07:56:49,413::resourceManager::155::ResourceManager.Request::(__init__) ResName=`608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498`ReqID=`9658cad8-0c8b-4528-bf7d-421d93d4ddc3`::Request was made in '/usr/share/vdsm/storage/volume.py' line '533' at 'prepare'
59092:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 07:56:49,414::resourceManager::463::ResourceManager::(registerResource) Trying to register resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498' for lock type 'exclusive'
59093:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 07:56:49,416::resourceManager::505::ResourceManager::(registerResource) Resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498' is free. Now locking as 'exclusive' (1 active user)
59095:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 07:56:49,420::resourceManager::192::ResourceManager.Request::(grant) ResName=`608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498`ReqID=`9658cad8-0c8b-4528-bf7d-421d93d4ddc3`::Granted request

The customer then attempted to merge again, in this instance we see the task hang waiting for the resource to become free..

70786:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 08:18:28,757::resourceManager::515::ResourceManager::(releaseResource) Trying to release resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498'
70803:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 08:18:29,346::resourceManager::530::ResourceManager::(releaseResource) Released resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498' (0 active users)
70805:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 08:18:29,347::resourceManager::535::ResourceManager::(releaseResource) Resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498' is free, finding out if anyone is waiting for it.
70816:dede6b50-f759-4d94-8bab-4c48bc6d6719::DEBUG::2012-10-09 08:18:29,898::resourceManager::542::ResourceManager::(releaseResource) No one is waiting for resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.63d2f649-ab16-4e89-90c5-f13218359498', Clearing records.

Version-Release number of selected component (if applicable):
113.3.el6_3

How reproducible:
Always.

Steps to Reproduce:
1. Follow the steps in BZ#864892.
2. Attempt to use the COW volume again.
  
Actual results:
VDSM does not unlock the COW volumes _lvmActivationNS resource during the teardown after the original issue.

Expected results:
VDSM should unlock the COW volumes _lvmActivationNS resource during the teardown after the original issue.

Additional info:
Comment 3 Lee Yarwood 2012-10-10 12:42:42 UTC 
I just noticed that I supplied the wrong example in comment #1. This is clearly a working example where the same task locks and then unlocks the resource after completing the merge....

The correct example showing a failed merge task lock but not unlock the resource before a separate merge task then attempts to lock the resource is below.


# grep -rin '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf' vdsm.log.1
60073:6bc892de-2b19-404a-9b31-fabdcc394a25::DEBUG::2012-10-09 07:57:07,522::resourceManager::155::ResourceManager.Request::(__init__) ResName=`608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf`ReqID=`474302db-f1ab-4b1e-86a5-51d8aa0cc48e`::Request was made in '/usr/share/vdsm/storage/volume.py' line '533' at 'prepare'
60075:6bc892de-2b19-404a-9b31-fabdcc394a25::DEBUG::2012-10-09 07:57:07,524::resourceManager::463::ResourceManager::(registerResource) Trying to register resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf' for lock type 'exclusive'
60089:6bc892de-2b19-404a-9b31-fabdcc394a25::DEBUG::2012-10-09 07:57:07,535::resourceManager::505::ResourceManager::(registerResource) Resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf' is free. Now locking as 'exclusive' (1 active user)
60093:6bc892de-2b19-404a-9b31-fabdcc394a25::DEBUG::2012-10-09 07:57:07,536::resourceManager::192::ResourceManager.Request::(grant) ResName=`608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf`ReqID=`474302db-f1ab-4b1e-86a5-51d8aa0cc48e`::Granted request
 
73114:39b07f28-02a1-4167-868a-3ff6b95ac2b2::DEBUG::2012-10-09 08:20:11,591::resourceManager::155::ResourceManager.Request::(__init__) ResName=`608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf`ReqID=`f16c755e-c590-4596-aab6-b6b1d642a18f`::Request was made in '/usr/share/vdsm/storage/volume.py' line '533' at 'prepare'
73115:39b07f28-02a1-4167-868a-3ff6b95ac2b2::DEBUG::2012-10-09 08:20:11,592::resourceManager::463::ResourceManager::(registerResource) Trying to register resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf' for lock type 'exclusive'
73116:39b07f28-02a1-4167-868a-3ff6b95ac2b2::DEBUG::2012-10-09 08:20:11,593::resourceManager::487::ResourceManager::(registerResource) Resource '608fea3a-824c-497a-9619-9546e4aab241_lvmActivationNS.fdd80dcf-5b90-455a-8cba-75f74130a7bf' is currently locked, Entering queue (1 in queue)
Comment 9 Ayal Baron 2012-10-21 09:07:52 UTC 

*** This bug has been marked as a duplicate of bug 815359 ***
Note You need to log in before you can comment on or make changes to this bug.