Description of problem: ======================= rebalance log is full of warning as below [2014-09-19 18:25:44.789690] W [dict.c:480:dict_unref] (-->/lib64/libc.so.6() [0x3a6be43bf0] (-->/usr/lib64/libglusterfs.so.0(synctask_wrap+0x12) [0x30ddc5ba62] (-->/usr/lib64/glusterfs/3.6.0.28/xlator/cluster/distribute.so(dht_migrate_file+0x43f) [0x7f7e56f6cf2f]))) 0-dict: dict is NULL had arounf 124 files and gor this warning for 100+ times. Version-Release number of selected component (if applicable): ============================================================= 3.6.0.28-1.el6rhs.x86_64 How reproducible: ================= always Steps to Reproduce: =================== 1.create distribiued volume , start and mount volume. crete data. 2. ass-brick to volume or perform few renames 3. start rebalance. 4. once rebalance is completed check log. [root@snapshot09 down]# grep 'dict is NULL' /var/log/glusterfs/down-rebalance.log | wc -l 124 log snippet:- [2014-09-19 18:25:44.601465] W [dict.c:480:dict_unref] (-->/lib64/libc.so.6() [0x3a6be43bf0] (-->/usr/lib64/libglusterfs.so.0(synctask_wrap+0x12) [0x30ddc5ba62] (-->/usr/lib64/glusterfs/3.6.0.28/xlator/cluster/distribute.so(dht_migrate_file+0x2a6) [0x7f7e56f6cd96]))) 0-dict: dict is NULL [2014-09-19 18:25:44.634925] W [dict.c:480:dict_unref] (-->/lib64/libc.so.6() [0x3a6be43bf0] (-->/usr/lib64/libglusterfs.so.0(synctask_wrap+0x12) [0x30ddc5ba62] (-->/usr/lib64/glusterfs/3.6.0.28/xlator/cluster/distribute.so(dht_migrate_file+0x43f) [0x7f7e56f6cf2f]))) 0-dict: dict is NULL [2014-09-19 18:25:44.690666] W [dict.c:480:dict_unref] (-->/lib64/libc.so.6() [0x3a6be43bf0] (-->/usr/lib64/libglusterfs.so.0(synctask_wrap+0x12) [0x30ddc5ba62] (-->/usr/lib64/glusterfs/3.6.0.28/xlator/cluster/distribute.so(dht_migrate_file+0x2a6) [0x7f7e56f6cd96]))) 0-dict: dict is NULL
Verified on 3.6.0.38-1.el6rhs.x86_64 Now 'dict is NULL' doesn't appear in rebalance logs
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-2015-0038.html