Bug 1257110

Summary:	Logging : unnecessary log message "REMOVEXATTR No data available " when files are written to glusterfs mount
Product:	[Community] GlusterFS	Reporter:	Vijay Bellur <vbellur>
Component:	logging	Assignee:	Vijay Bellur <vbellur>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, cmptuomp3, jthottan, rabhat
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1248941	Environment:
Last Closed:	2016-06-16 13:33:45 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:	1248941
Bug Blocks:

Description Vijay Bellur 2015-08-26 09:54:05 UTC

+++ This bug was initially created as a clone of Bug #1248941 +++

Description of problem: REMOVEXATTR No data available in log when files are written to glusterfs mount


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


How reproducible: very


Steps to Reproduce:
1. write file in glusterfs mount (# touch /ssd_data/test)
2. 
3.

Actual results:
# tail -n 1 /var/log/glusterfs/ssd_data.log
[2015-07-31 07:51:07.354206] W [fuse-bridge.c:1263:fuse_err_cbk] 0-glusterfs-fuse: 362196675: REMOVEXATTR() /test => -1 (No data available)


Expected results:
no error in log

Additional info:

Comment 1 Anand Avati 2015-08-26 10:12:50 UTC

REVIEW: http://review.gluster.org/12015 (mount/fuse: Avoid logging ENODATA in {f}removexattr) posted (#1) for review on master by Vijay Bellur (vbellur)

Comment 2 Anand Avati 2015-08-27 07:41:30 UTC

REVIEW: http://review.gluster.org/12015 (mount/fuse: Log ENODATA as DEBUG in {f}removexattr) posted (#2) for review on master by Vijay Bellur (vbellur)

Comment 3 Anand Avati 2015-08-28 12:33:42 UTC

COMMIT: http://review.gluster.org/12015 committed in master by Raghavendra Bhat (raghavendra) 
------
commit bd9dd34700de63f96b9fc65125d539b2c16fa6bf
Author: Vijay Bellur <vbellur>
Date:   Wed Aug 26 15:24:39 2015 +0530

    mount/fuse: Log ENODATA as DEBUG in {f}removexattr
    
    Logging ENODATA errors for {f}removexattr at a higher loglevel does not
    add a lot of value and causes a log message flood as per multiple reports.
    
    Added a new cbk, fuse_removexattr_cbk() to be used with removexattr fops.
    ENODATA now gets logged at loglevel DEBUG in fuse_removexattr_cbk(). This also
    prevents more conditional checks in the common fuse_err_cbk() callback.
    
    Change-Id: I1585b4d627e0095022016c47d7fd212018a7194b
    BUG: 1257110
    Signed-off-by: Vijay Bellur <vbellur>
    Reviewed-on: http://review.gluster.org/12015
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Bhat <raghavendra>

Comment 4 Niels de Vos 2016-06-16 13:33:45 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user