Bug 1425676

Summary: gfids are not populated in release/releasedir requests
Product: [Community] GlusterFS Reporter: Pranith Kumar K <pkarampu>
Component: protocolAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.11.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-30 18:44:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pranith Kumar K 2017-02-22 04:38:05 UTC
Description of problem:
    It is difficult to match opendir/releasedir or
    open/release calls without gfid associlation to find
    fd-leaks on the bricks. So assigning gfid also in
    the request which was already there in the on-wire
    format.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-02-22 04:39:13 UTC
REVIEW: https://review.gluster.org/16706 (protocol/client: Add gfid in request for better tcpdumps) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 2 Worker Ant 2017-02-27 05:25:04 UTC
REVIEW: https://review.gluster.org/16706 (protocol/client: Add gfid in request for better tcpdumps) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 3 Worker Ant 2017-02-28 04:28:10 UTC
COMMIT: https://review.gluster.org/16706 committed in master by Raghavendra G (rgowdapp) 
------
commit 874059dc94a123f78c19ba14bee2d5540c106a9e
Author: Pranith Kumar K <pkarampu>
Date:   Wed Feb 22 09:49:05 2017 +0530

    protocol/client: Add gfid in request for better tcpdumps
    
    It is difficult to match opendir/releasedir or
    open/release calls without gfid associlation to find
    fd-leaks on the bricks. So assigning gfid also in
    the request which was already there in the on-wire
    format.
    
    BUG: 1425676
    Change-Id: Iec908eeaa2f97295d45140a529b7f8fb834a1553
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: https://review.gluster.org/16706
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 4 Shyamsundar 2017-05-30 18:44:46 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/