Description of problem: In disperse volumes, the following logs flood the brick log files : [2015-12-08 09:14:57.452707] W [dict.c:1282:dict_foreach_match] (-->/usr/lib64/glusterfs/3.7.5/xlator/features/index.so(+0x4b37) [0x7f9f64084b37] -->/usr/lib64/glusterfs/3.7.5/xlator/features/index.so(+0x4ae0) [0x7f9f64084ae0] -->/usr/lib64/libglusterfs.so.0(dict_foreach_match+0xdf) [0x7f9f73b2b39f] ) 0-dict: dict|match|action is NULL [Invalid argument] Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Those logs messages should not occur. Additional info: Thanks to Nithya Balachandran for pointing it out.
Steps to reproduce: 1] Created 4+2 EC vol 2] Fuse mount on client 3] Initiated some IO Brick logs flooded with message: [2015-12-25 02:57:44.071028] W [dict.c:1282:dict_foreach_match] (-->/usr/lib64/glusterfs/3.7.5/xlator/features/index.so(index_fill_zero_array+0xc) [0x7fea119faaec] -->/usr/lib64/glusterfs/3.7.5/xlator/features/index.so(+0x3a8a) [0x7fea119faa8a] -->/lib64/libglusterfs.so.0(dict_foreach_match+0xe3) [0x7fea25b22c73] ) 0-dict: dict|match|action is NULL [Invalid argument] glusterfs-3.7.5-10.el7rhgs.x86_64 Not able to reproduce this with latest build "glusterfs-3.7.5-13.el7rhgs.x86_64", moving it to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html