Bug 1246728

Summary: client3_3_removexattr_cbk floods the logs with "No data available" messages
Product: [Community] GlusterFS Reporter: Con Tassios <ct>
Component: loggingAssignee: Niels de Vos <ndevos>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.2CC: bugs, gluster-bugs, ndevos
Target Milestone: ---Keywords: EasyFix, Regression, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1246736 (view as bug list) Environment:
Last Closed: 2015-07-30 09:50:10 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:
Bug Depends On: 1246736    
Bug Blocks:    

Description Con Tassios 2015-07-25 05:09:41 UTC 
Similar problem to https://bugzilla.redhat.com/show_bug.cgi?id=1188064

With log-level set to ERROR, I still get logs like this

[2015-07-25 02:06:11.206465]  [MSGID: 114031] [client-rpc-fops.c:1300:client3_3_removexattr_cbk] 0-gv0-client-0: remote operation failed: No data available [No data available]                   

I notice that xlators/protocol/client/src/client-rpc-fops.c line 1293 of 3.7.2 source, loglevel is set to 0.  The 3.6.4 source set this to GF_LOG_DEBUG.
Comment 1 Anand Avati 2015-07-25 08:58:06 UTC 
REVIEW: http://review.gluster.org/11760 (logging: client3_3_removexattr_cbk should not log expected ENODATA) posted (#1) for review on release-3.7 by Niels de Vos (ndevos)
Comment 2 Anand Avati 2015-07-26 08:10:53 UTC 
COMMIT: http://review.gluster.org/11760 committed in release-3.7 by Niels de Vos (ndevos) 
------
commit 285d1c851d18bcd7e7a2c48f440bbe107d260dca
Author: Niels de Vos <ndevos>
Date:   Sat Jul 25 10:47:03 2015 +0200

    logging: client3_3_removexattr_cbk should not log expected ENODATA
    
    Commit 379dbbfd changed the log level of an expected error message from
    GF_LOG_DEBUG to '0'. This causes the message to always get logged. It is
    intended to log the warning when the xattr could not be removed (but
    exists), removing a non-existing xattr is sufficient as debug.
    
    Backported from:
    > BUG: 1246736
    > Change-Id: If11d15d699e8152cc32e0c0c1d65b587c5c48892
    > Reviewed-on: http://review.gluster.org/11759
    > Signed-off-by: Niels de Vos <ndevos>
    
    Change-Id: If11d15d699e8152cc32e0c0c1d65b587c5c48892
    BUG: 1246728
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: http://review.gluster.org/11760
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Joe Julian <me>
    Tested-by: Joe Julian <me>
    Tested-by: Gluster Build System <jenkins.com>
Comment 3 Kaushal 2015-07-30 09:50:10 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.7.3, please open a new bug report.

glusterfs-3.7.3 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user