Bug 1441574

Summary:	[geo-rep]: rsync should not try to sync internal xattrs
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	geo-replication	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.8	CC:	avishwan, bugs, chrisw, csaba, khiremat, nlevinki, otira.fuu, rhinduja, rkavunga, sarumuga, storage-qa-internal, vnosov
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8.12	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1353952	Environment:
Last Closed:	2017-05-29 04:58:58 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:	1353952
Bug Blocks:	1440754

Comment 1 Worker Ant 2017-04-12 08:58:49 UTC

REVIEW: https://review.gluster.org/17045 (geo-rep: filter out xtime attribute during getxattr) posted (#1) for review on release-3.8 by mohammed rafi  kc (rkavunga)

Comment 2 Worker Ant 2017-05-03 08:19:50 UTC

COMMIT: https://review.gluster.org/17045 committed in release-3.8 by Niels de Vos (ndevos) 
------
commit 6a5d9764e687b74b0686d492120584e88a6f8110
Author: Saravanakumar Arumugam <sarumuga>
Date:   Fri Jul 8 19:10:45 2016 +0530

    geo-rep: filter out xtime attribute during getxattr
    
    georep gsyncd's xtime needs to filtered irrespective
    of any process access.
    
    This way, we can avoid (unnecessarily)syncing xtime attribute
    to slave, which may raise permission denied errors.
    
    test case modified to check for xtime xattr only in backend.
    Back port of>
    >Change-Id: I2390b703048d5cc747d91fa2ae884dc55de58669
    >BUG: 1353952
    >Signed-off-by: Saravanakumar Arumugam <sarumuga>
    >Signed-off-by: Mohammed Rafi KC <rkavunga>
    >Reviewed-on: https://review.gluster.org/14880
    >Smoke: Gluster Build System <jenkins.org>
    >Reviewed-by: Kotresh HR <khiremat>
    >Tested-by: Kotresh HR <khiremat>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    
    Change-Id: Ibdee6f3093648a7e0fb1e2b6be8172e604ab657f
    BUG: 1441574
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: https://review.gluster.org/17045
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Kotresh HR <khiremat>
    Reviewed-by: Niels de Vos <ndevos>

Comment 3 Niels de Vos 2017-05-29 04:58:58 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-3.8.12, please open a new bug report.

glusterfs-3.8.12 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] https://lists.gluster.org/pipermail/announce/2017-May/000072.html
[2] https://www.gluster.org/pipermail/gluster-users/