[Gluster-users] Gluster v3.7.3 REMOVEXATTR clogs volume logs

[Glomski, Patrick]

I am currently testing gluster v3.7.3 on Scientific Linux 7.1 and a newly
created gluster volume. After transferring some files to the volume over
the fuse mount, the volume log is flooded with 2.5GB of errors like the
following:

[2015-08-13 15:54:36.921622] W [fuse-bridge.c:1230:fuse_err_cbk]
0-glusterfs-fuse: 361669: REMOVEXATTR() /path/to/file => -1 (No data
available)

There are several (fixed) redhat bugs relating to similar errors:
https://bugzilla.redhat.com/show_bug.cgi?id=1245966
https://bugzilla.redhat.com/show_bug.cgi?id=1188064
https://bugzilla.redhat.com/show_bug.cgi?id=1192832

- Is anyone else running 3.7 seeing similar errors?
- Is there something wrong with my configuration?
- If it's a problem, what other information do you need to diagnose?

gluster volume info:

Volume Name: testbrick
Type: Distribute
Volume ID: 91b0d825-5e39-4b17-a505-174b47849b40
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: gfstest:/data/brick01/testbrick
Options Reconfigured:
performance.readdir-ahead: on

Thanks,
Patrick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150813/61093920/attachment.html>