Description of problem: Error messages are getting logged on brick logs while creating directories on fuse mount for disperse volumes. Version-Release number of selected component (if applicable): [root@aspandey gfsa]# gluster --version glusterfs 3.8dev built on Jun 12 2015 18:03:10 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. How reproducible: 100% Steps to Reproduce: 1. Create disperse volume 1 x (4+2) 2. mount as glusterfs on a mount point /mnt 3. create a directory on mount point i.e. /mnt See the brick logs. Following error messages are present - [2015-06-12 12:35:14.351684] I [MSGID: 115029] [server-handshake.c:588:server_setvolume] 0-gfs-server: accepted client from aspandey-8997-2015/06/12-12:35:14:330840-gfs-client-0-0-0 (version: 3.8dev) [2015-06-12 12:35:23.789708] E [posix-helpers.c:1087:posix_handle_pair] 0-gfs-posix: /brick/gluster/rep/A1/dir: key:glusterfs.inodelk-dom-count flags: 1 length:15 error:Operation not supported [2015-06-12 12:35:23.789731] E [posix.c:1386:posix_mkdir] 0-gfs-posix: setting xattrs on /brick/gluster/rep/A1/dir failed (Operation not supported) Actual results: Misleading error messages in brick logs. Expected results: There should not be any error message for successful fop's for example directory creation (mkdir). Additional info:
http://review.gluster.org/11204
REVIEW: http://review.gluster.org/11204 ( locks: Filter virtual xattrs in locks for all the fops) posted (#2) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/11204 ( locks: Filter virtual xattrs in locks for all the fops) posted (#3) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/11204 ( locks: Filter virtual xattrs in locks for all the fops) posted (#4) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/11204 ( locks: Filter virtual xattrs in locks for all the fops) posted (#5) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/11204 ( locks: Filter virtual xattrs in locks for all the fops) posted (#6) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/11957 ( locks: Filter virtual xattrs in locks for all the fops) posted (#1) for review on release-3.7 by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/13266 (cluster/ec: Use correct log levels) posted (#1) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/13266 (cluster/ec: Use correct log levels) posted (#2) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/13266 (cluster/ec: Use correct log levels) posted (#3) for review on master by Ashish Pandey (aspandey)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
REVIEW: http://review.gluster.org/13266 (cluster/ec: Use correct log levels) posted (#4) for review on master by Ashish Pandey (aspandey)
COMMIT: http://review.gluster.org/13266 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 02b2750ecc35f88c3262015b401dda962381f9da Author: Ashish Pandey <aspandey> Date: Wed Jan 20 14:30:08 2016 +0530 cluster/ec: Use correct log levels Problem : Misleading messages are getting logged in mount logs and bricks log. "Mismatching xdata" and "Heal failed" are getting logged Solution : Reduce the level of logs from INFO, WARNING and NOTICE to DEBUG level wherever applicable OR use fop_log_level to get proper log level. Change-Id: Ia824c71e75ab683d3cb8949e1966ea09c9ccce72 BUG: 1231224 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/13266 Smoke: Gluster Build System <jenkins.com> Reviewed-by: Xavier Hernandez <xhernandez> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
REVIEW: http://review.gluster.org/11204 (locks: Filter virtual xattrs in locks for all the fops) posted (#7) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/11204 (feature/locks: Implement fops in locks Translator) posted (#8) for review on master by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/11204 (feature/locks: Implement fops in locks Translator) posted (#9) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/11204 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 68b23745602e4cc6317d6dce72ed0392d4174972 Author: Ashish Pandey <aspandey> Date: Thu Aug 25 11:49:19 2016 +0530 feature/locks: Implement fops in locks Translator Implement those fop which were not present in locks translator. Also make sure to return xdata with the entries which were requested for these fops. Change-Id: I6e7f80e9eb5fba9e34c7034f6bc30557cde20927 BUG: 1231224 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/11204 Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
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.10.0, please open a new bug report. glusterfs-3.10.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://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/