+++ This bug was initially created as a clone of Bug #1246728 +++ 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.
REVIEW: http://review.gluster.org/11759 (logging: client3_3_removexattr_cbk should not log expected ENODATA) posted (#1) for review on master by Niels de Vos (ndevos)
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