[Bugs] [Bug 1390914] New: Glusterfs create a flock lock by anonymous fd, but can' t release it forever.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1390914

            Bug ID: 1390914
           Summary: Glusterfs create a flock lock by anonymous fd, but
                    can't release it forever.
           Product: GlusterFS
           Version: 3.6.9
         Component: protocol
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: xiaoping.wu at nokia.com
                CC: bugs at gluster.org



Created attachment 1216401
  --> https://bugzilla.redhat.com/attachment.cgi?id=1216401&action=edit
sn-0_mnt-bricks-services-brick.log is the glusterfs server log from sn-0.
sn-1_mnt-bricks-services-brick.log is glusterfs server log from sn-1.
lmn_mnt-services.log is glusterfs client log from lmn-0

Description of problem:
 - when tcp connection is connected between server and client, but AFR didn't
get CHILD_UP event. if application open a file for flock operation. AFR would
send the open fop to the CHILD client.
 - But the flock fop could be sent to server with a anonymous fd(-2), server
could flock successfully.
 - When application release the flock, client can't send the release request to
server, so server can't release the flock forever.

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

How reproducible:
 - In my env, there are a replicate volume, one brick locate in sn-0 VM,
another brick locate in sn-1 VM.
 - glusterfs client locate in lmn-0 VM, sn-0, sn-1.
 - This issue isn't easy to reproduce.

Steps to Reproduce:
1. when restart sn-0/sn-1 at the same time.
2. glusterfs server on sn-0/sn-1 startup.
3. application on lmn-0 VM will open a file to do flock.

Actual results:
1. AFR get flock from sn-0 successfully by actual fd.
2  AFR get flock form sn-1 successfully by anonymous fd(-2).
3. when application release flock, the flock on sn-1 can't be release because
release request didn't sent to server.


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.