Bug 1163571

Summary:	bulk remove xattr should not fail if removexattr fails with ENOATTR/ENODATA
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	posix	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v3.6.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1160509	Environment:
Last Closed:	2016-02-04 15:05:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1160509
Bug Blocks:	1162226

Description Pranith Kumar K 2014-11-13 03:21:55 UTC

+++ This bug was initially created as a clone of Bug #1160509 +++

Description of problem:
    Bulk remove xattr is internal fop that comes from afr metadata
    self-heal. some xattrs like removexattr("posix.system_acl_access"),
    removes more than one xattr on the file so removexattr on these
    xattrs will fail with either ENODATA/ENOATTR. Since all afr cares
    is removing of these xattrs and if they are already deleted, it can
    treat it as success.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Anand Avati on 2014-11-04 23:01:48 EST ---

REVIEW: http://review.gluster.org/9049 (storage/posix: Treat ENODATA/ENOATTR as success in bulk removexattr) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)

--- Additional comment from Anand Avati on 2014-11-05 11:33:29 EST ---

REVIEW: http://review.gluster.org/9049 (storage/posix: Treat ENODATA/ENOATTR as success in bulk removexattr) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)

--- Additional comment from Anand Avati on 2014-11-06 00:42:56 EST ---

COMMIT: http://review.gluster.org/9049 committed in master by Vijay Bellur (vbellur) 
------
commit b42255e87a06679b803e6bd83d02465d82c357b6
Author: Pranith Kumar K <pkarampu>
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>
    Reviewed-on: http://review.gluster.org/9049
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 1 Anand Avati 2014-11-13 03:24:08 UTC

REVIEW: http://review.gluster.org/9109 (storage/posix: Treat ENODATA/ENOATTR as success in bulk removexattr) posted (#1) for review on release-3.6 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2014-11-17 07:08:39 UTC

COMMIT: http://review.gluster.org/9109 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit 4e8901f7201ec68f30dbdf452362fcf0f3ec16bc
Author: Pranith Kumar K <pkarampu>
Date:   Wed Nov 5 09:04:50 2014 +0530

    storage/posix: Treat ENODATA/ENOATTR as success in bulk removexattr
    
            Backport of http://review.gluster.org/9049
    
    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.
    
    BUG: 1163571
    Change-Id: I009f4736f8b6362d7115f57a7d7aece74e56e4f6
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/9109
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Kaushal 2016-02-04 15:05:34 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v3.6.2, please open a new bug report.

glusterfs-v3.6.2 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978top
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Kaushal 2016-02-04 15:08:06 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v3.6.2, please open a new bug report.

glusterfs-v3.6.2 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2015/01/glusterfs-3-6-2-ga-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user