[Bugs] [Bug 1385236] invalid argument warning messages seen in fuse client logs 2016-09-30 06: 34:58.938667] W [dict.c:418ict_set] (-->/usr/lib64/glusterfs/3.8.4/xlator/ cluster/replicate.so(+0x58722) 0-dict: !this || !value for key= link-count [Invalid argument]

bugzilla at redhat.com bugzilla at redhat.com
Sun Oct 16 02:38:28 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1385236



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15650 committed in release-3.9 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit 07d8f2b26071fa6c757190ce1a792e07d0d744b8
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Fri Sep 30 17:16:43 2016 +0530

    cluster/afr: Prevent dict_set() on NULL dict

    In afr lookup when NULL dict is received in lookup, afr
    is supposed to set all the xattrs it requires in a new dict
    it creates, but for 'link-count' it is trying to set to the
    dict that is passed in lookup which can be NULL sometimes.
    This is leading to error logs. Fixed the same in this patch.

     >BUG: 1385104
     >Change-Id: I679af89cfc410cbc35557ae0691763a05eb5ed0e
     >Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
     >Reviewed-on: http://review.gluster.org/15646
     >Smoke: Gluster Build System <jenkins at build.gluster.org>
     >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
     >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
     >Reviewed-by: Ravishankar N <ravishankar at redhat.com>

    BUG: 1385236
    Change-Id: I802e74e7ad24e183b6653101ad7bf5ab0bf6e55b
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/15650
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list