Bug 1105083

Summary: Dist-geo-rep : geo-rep failed to sync some files, with error "(Operation not permitted)" on slaves.
Product: [Community] GlusterFS Reporter: Aravinda VK <avishwan>
Component: geo-replicationAssignee: Aravinda VK <avishwan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: mainlineCC: aavati, avishwan, bugs, csaba, david.macdonald, gluster-bugs, khiremat, nlevinki, nsathyan, rhs-bugs, ssamanta, vshankar
Target Milestone: ---Keywords: TestBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.6.0beta1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1102550 Environment:
Last Closed: 2014-11-11 08:34:23 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: 1102550    
Bug Blocks:    

Comment 1 Anand Avati 2014-06-05 11:00:57 UTC
REVIEW: http://review.gluster.org/7972 (geo-rep: entry_ops errors handling) posted (#2) for review on master by Aravinda VK (avishwan)

Comment 2 Aravinda VK 2014-06-05 11:02:56 UTC
This patch also required to fix the issue completely.
http://review.gluster.org/#/c/7978/

Comment 3 Anand Avati 2014-06-06 10:23:22 UTC
REVIEW: http://review.gluster.org/7972 (geo-rep: entry_ops errors handling) posted (#3) for review on master by Aravinda VK (avishwan)

Comment 4 Anand Avati 2014-06-12 06:53:00 UTC
COMMIT: http://review.gluster.org/7972 committed in master by Venky Shankar (vshankar) 
------
commit f25c88375b0fc03a97a423b565217fb9b55f7850
Author: Aravinda VK <avishwan>
Date:   Wed Jun 4 17:41:10 2014 +0530

    geo-rep: entry_ops errors handling
    
    Xattr.lsetxattr_l call will not raise OSError which
    errno_wrap can handle, so we need to use Xattr.lsetxattr
    to get proper OSError and errno_wrap ignores or retries
    accordingly.
    
    Change-Id: Ie0a777152ddbaf9ed80c977e4704974fec997bea
    BUG: 1105083
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/7972
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Venky Shankar <vshankar>

Comment 5 Niels de Vos 2014-09-22 12:42:09 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 6 Niels de Vos 2014-11-11 08:34:23 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users