[Bugs] [Bug 1248941] Logging : unnecessary log message "REMOVEXATTR No data available " when files are written to glusterfs mount

[bugzilla at redhat.com]

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



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12041 committed in release-3.7 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit b1cd5cb8a857ed3a95eab95179378283c8d41763
Author: Vijay Bellur <vbellur at redhat.com>
Date:   Wed Aug 26 15:24:39 2015 +0530

    mount/fuse: Log ENODATA as DEBUG in {f}removexattr

    Logging ENODATA errors for {f}removexattr at a higher loglevel does not
    add a lot of value and causes a log message flood as per multiple reports.

    Added a new cbk, fuse_removexattr_cbk() to be used with removexattr fops.
    ENODATA now gets logged at loglevel DEBUG in fuse_removexattr_cbk(). This
also
    prevents more conditional checks in the common fuse_err_cbk() callback.

    Change-Id: I1585b4d627e0095022016c47d7fd212018a7194b
    BUG: 1248941
    Signed-off-by: Vijay Bellur <vbellur at redhat.com>
    Reviewed-on: http://review.gluster.org/12015
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-on: http://review.gluster.org/12041

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