Bug 1135016 - getxattr and other filesystem ops fill the logs with useless errors (expected EPERM and the like)
Summary: getxattr and other filesystem ops fill the logs with useless errors (expected...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: 3.5.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-28 16:31 UTC by Peter Auyeung
Modified: 2016-06-17 15:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-17 15:58:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1037511 0 unspecified CLOSED Operation not permitted occurred during setattr of <nul> 2021-02-22 00:41:40 UTC

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.


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