[Bugs] [Bug 1160509] bulk remove xattr should not fail if removexattr fails with ENOATTR/ENODATA

[bugzilla at redhat.com]

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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9049 committed in master by Vijay Bellur
(vbellur at redhat.com) 
------
commit b42255e87a06679b803e6bd83d02465d82c357b6
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Wed Nov 5 09:04:50 2014 +0530

    storage/posix: Treat ENODATA/ENOATTR as success in bulk removexattr

    Bulk remove xattr is internal fop in gluster. Some of the xattrs may have
    special behavior. Ex: removexattr("posix.system_acl_access"), removes more
than
    one xattr on the file that could be present in the bulk-removal request.
    Removexattr of these deleted xattrs will fail with either ENODATA/ENOATTR.
    Since all this fop cares is removal of the xattrs in bulk-remove request
and
    if they are already deleted, it can be treated as success.

    Change-Id: Id8f2a39b68ab763ec8b04cb71b47977647f22da4
    BUG: 1160509
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/9049
    Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=xislSirATU&a=cc_unsubscribe