Description of problem: Log flooding of [2018-05-08 07:45:38.612289] I [dict.c:471:dict_get] (-->/usr/lib64/glusterfs/3.12.2/xlator/cluster/distribute.so(+0x209e0) [0x7f13d2dc09e0] -->/usr/lib64/glusterfs/3.12.2/xlator/cluster/distribute.so(+0x41605) [0x7f13d2de1605] -->/lib64/libglusterfs.so.0(dict_get+0x10c) [0x7f13e0e0dacc] ) 2-dict: !this || key=trusted.glusterfs.dht.mds [Invalid argument] Version-Release number of selected component (if applicable): 3.12.2-8 How reproducible: 100% Steps to Reproduce: 1. create a arbiter volume 2. run fileop tool using mount -t nfs -o vers=4 rhsqe-repo.lab.eng.blr.redhat.com:/ /opt /opt/qa/tools/system_light/run.sh -w /mnt/nfsv4 -t fileop -l /var/tmp/out.log 3. Check the mount log Actual results: Logg flooding with [2018-05-08 07:45:38.612289] I [dict.c:471:dict_get] (-->/usr/lib64/glusterfs/3.12.2/xlator/cluster/distribute.so(+0x209e0) [0x7f13d2dc09e0] -->/usr/lib64/glusterfs/3.12.2/xlator/cluster/distribute.so(+0x41605) [0x7f13d2de1605] -->/lib64/libglusterfs.so.0(dict_get+0x10c) [0x7f13e0e0dacc] ) 2-dict: !this || key=trusted.glusterfs.dht.mds [Invalid argument] Expected results: No log flooding should be there Additional info: SOs reports at newtsuit under BZ_report/<bug-id>
I guess this is the fix? https://review.gluster.org/19981
Verified this BZ on glusterfs version glusterfs-3.12.2-10. Followed below steps: 1) Created a arbiter volume and started it. 2) FUSE mounted on a client. 3) Ran fileop tool using mount -t nfs -o vers=4 rhsqe-repo.lab.eng.blr.redhat.com:/ /opt /opt/qa/tools/system_light/run.sh -w /mnt/arbiter -t fileop -l /var/tmp/out.log 4) While the script in step-3 is in-progress, added 3 bricks to the arbiter volume. In client mount logs, didn't see flooding of log messages "-dict: !this || key=trusted.glusterfs.dht.mds [Invalid argument]". These messages are only seen 3 times. Moving this BZ 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://access.redhat.com/errata/RHSA-2018:2607