Bug 803637 - nfs-nlm: lock not honoured if tried from different clients on same file
Summary: nfs-nlm: lock not honoured if tried from different clients on same file
Keywords:
Status: CLOSED NOTABUG
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-15 10:28 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-02 10:26:07 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Saurabh 2012-03-15 10:28:21 UTC 
Description of problem:
mounted the same file on different clients and then tried to put up the exclusive  lock on same region of single file. both of them were able to hold the lock.

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

How reproducible:
always

Steps to Reproduce:
1. nfs mount a volume on two different clients
2. try to put the lock on same region of same file 
3.
  
Actual results:
the lock is simultaneously acquired

Expected results:
if lock is already held then other other should as lock mechanism used in script is blocking locks.

Additional info:
Comment 1 Krishna Srinivas 2012-03-19 12:03:51 UTC 
Just confirmed with Saurabh that there was a problem with the test script. Exclusive locking is working fine.
Note You need to log in before you can comment on or make changes to this bug.