Bug 802767 - nfs-nlm:unlock within grace-period fails
Summary: nfs-nlm:unlock within grace-period fails
Keywords:
Status: CLOSED DUPLICATE of bug 802885
Alias: None
Product: GlusterFS
Classification: Community
Component: nfs
Version: pre-release
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Vinayaga Raman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-13 13:19 UTC by Saurabh
Modified: 2016-01-19 06:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-03 08:00:05 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.