Bug 802767

Summary:	nfs-nlm:unlock within grace-period fails
Product:	[Community] GlusterFS	Reporter:	Saurabh <saujain>
Component:	nfs	Assignee:	Vinayaga Raman <vraman>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	pre-release	CC:	gluster-bugs, mzywusko, rwheeler, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-03 08:00:05 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:

Description Saurabh 2012-03-13 13:19:23 UTC

Description of problem:
the unlock within the grace-period fails, after the nfs server restart.

This may be because of non-reclamation of the locks earlier generated


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


How reproducible:
tried it once


Steps to Reproduce:
1. put a lock on a file
2. kill the nfs server
3. bring back the nfs server before 50 seconds
4. try to unlock the file 
  
Actual results:
the unlock fails with the error message as, 
returns:- nlm_get_uniq() returned NULL and  
unable to unlock_fd_resume


Expected results:
it should have unlocked the lock previously held after reclaiming it with in grace period 

Additional info:

Comment 1 Krishna Srinivas 2012-04-03 08:00:05 UTC


*** This bug has been marked as a duplicate of bug 802885 ***