Bug 1135016

Summary:	getxattr and other filesystem ops fill the logs with useless errors (expected EPERM and the like)
Product:	[Community] GlusterFS	Reporter:	Peter Auyeung <pauyeung>
Component:	logging	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.2	CC:	bugs, ndevos
Target Milestone:	---	Keywords:	EasyFix, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-17 15:58:30 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 Peter Auyeung 2014-08-28 16:31:12 UTC

Description of problem:
When a non-privilege user perform filesystem operations e.g. ls, move, delete...etc over gluster NFS, we got errors on brick logs.
 

Version-Release number of selected component (if applicable):
Gluster 3.5.2
Ubuntu 12.04
xfs bricks

How reproducible:
as non-privilege user, do an "ls " on nfs mount to gluster

Steps to Reproduce:
1.$ ls -ltar
ls: jrose: Permission denied



Actual results:

error on brick logs
[2014-08-28 16:16:34.324009] E [marker.c:327:marker_getxattr_cbk] 0-sas03-marker: dict is null
[2014-08-28 16:16:34.324047] E [server-rpc-fops.c:796:server_getxattr_cbk] 0-sas03-server: 8647789: GETXATTR /DevMordorHomeSata03//jrose (043f2d28-7bf4-44ef-8b91-a68bf004058d) ((null)) ==> (Permission denied)

Expected results:
No error on logs

Additional info:

This could be similar to these bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1037511

Comment 1 Niels de Vos 2014-10-25 17:25:00 UTC

Indeed, these messages in the bricks should not be marked as Error, but rather as Debug. There have been some related changes in newer versions, but none of then seem to address this issue.

Comment 2 Niels de Vos 2016-06-17 15:58:30 UTC

This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.