Bug 799930

Summary: lockf: F_TEST always fails on gNFS
Product: [Community] GlusterFS Reporter: Sachidananda Urs <sac>
Component: nfsAssignee: Vinayaga Raman <vraman>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: pre-releaseCC: amarts, gluster-bugs, rwheeler, vinaraya
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-04 12:31:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: DP CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
fcntl version none

Description Sachidananda Urs 2012-03-05 12:51:02 UTC 
Description of problem:

lockf(int filedes, int function, off_t size) always fails on gNFS (works on kernel NFS and FUSE though).

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

3.3.0qa25

How reproducible:

Always.

Steps to Reproduce:

Program attached.
  
Actual results:

lockf fails.

Expected results:

lockf should pass.
Comment 1 Sachidananda Urs 2012-03-05 13:14:42 UTC 
Created attachment 567606 [details]
fcntl version
Comment 2 Krishna Srinivas 2012-03-08 13:36:26 UTC 
This behavior was seen as kernel lockd was also running. We can close this bug. We have to document that glusterfs-NLM can not run when lockd is also running.
Comment 3 Amar Tumballi 2012-03-12 09:46:26 UTC 
please update these bugs w.r.to 3.3.0qa27, need to work on it as per target milestone set.
Comment 4 Sachidananda Urs 2012-03-12 12:07:51 UTC 
Works when there is no kernel NFS mount on the machine.

However, this needs to be documented. Kris, can we keep this till documentation is in place?
Comment 5 Amar Tumballi 2012-03-13 07:02:51 UTC 
We can document this behavior. But we need to fix the root cause of kernel NFSv4 being present failing our NLM.
Comment 6 Vidya Sakar 2012-03-20 12:09:13 UTC 
Documented in the known issues section for beta1. To be investigated for beta2.
Comment 7 Krishna Srinivas 2012-04-04 12:31:47 UTC 

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