Bug 1008839

Summary:	Certain blocked entry lock info not retained after the lock is granted
Product:	[Community] GlusterFS	Reporter:	Anuradha <atalur>
Component:	locks	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, smohan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.3 (or later)	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 03:35:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Anuradha 2013-09-17 07:26:56 UTC

Description of problem:

When a blocked entry lock is granted and moved to granted state, a new entrylk is taken instead of retaining the old one. Leading to missing info of the entrylk in question, eg. blocked time of the entrylk. The old lock needs to be retained.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2013-09-17 10:08:35 UTC

REVIEW: http://review.gluster.org/5955 (features/locks : Certain blocked entry lock info not retained                  after the lock is granted) posted (#1) for review on master by Anuradha Talur (atalur)

Comment 2 Anand Avati 2013-09-17 10:24:44 UTC

REVIEW: http://review.gluster.org/5955 (features/locks : Certain blocked entry lock info not retained after the lock is granted) posted (#2) for review on master by Anuradha Talur (atalur)

Comment 3 Pranith Kumar K 2014-01-03 12:15:57 UTC

Anuradha already sent the patch. Assigning it to her.

Comment 4 Mike McCune 2016-03-28 22:17:27 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 7 Amar Tumballi 2018-08-29 03:35:57 UTC

This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.