Bug 1035639 - fuse release_cbk not implemented warning logs are shown in the logs
Summary: fuse release_cbk not implemented warning logs are shown in the logs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 08:59 UTC by Pranith Kumar K
Modified: 2014-11-11 08:24 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of:
Environment:
Last Closed: 2014-11-11 08:24:57 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Pranith Kumar K 2013-11-28 08:59:41 UTC
Description of problem:
The following logs appear in the log file sometimes.
[2013-11-28 08:58:23.727436] W [defaults.c:1381:default_release] (-->/usr/local/lib/glusterfs/3git/xlator/cluster/replicate.so(afr_local_cleanup+0x277) [0x7f03ad779770] (-->/usr/local/lib/libglusterfs.so.0(fd_unref+0x9d) [0x7f03b1c5dd2a] (-->/usr/local/lib/libglusterfs.so.0(+0x4dbce) [0x7f03b1c5dbce]))) 0-fuse: xlator does not implement release_cbk

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2013-11-28 09:03:55 UTC
REVIEW: http://review.gluster.org/6375 (mount/fuse: Prevent release_cbk not implemented warning) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2013-11-28 16:50:31 UTC
COMMIT: http://review.gluster.org/6375 committed in master by Vijay Bellur (vbellur) 
------
commit bca9eab359710eb3b826c6441126e2e56f774df5
Author: Pranith Kumar K <pkarampu>
Date:   Thu Nov 28 14:15:29 2013 +0530

    mount/fuse: Prevent release_cbk not implemented warning
    
    Change-Id: I53f0cb30f62ee9154670debf92476a51d6156844
    BUG: 1035639
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/6375
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2014-09-22 12:33:03 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:24:57 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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