Bug 1156405

Summary: geo-replication fails with dispersed volumes
Product: [Community] GlusterFS Reporter: Xavi Hernandez <jahernan>
Component: disperseAssignee: Xavi Hernandez <jahernan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: bugs, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.6.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1156404 Environment:
Last Closed: 2014-11-10 15:14:25 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: 1156404    
Bug Blocks: 1117822    

Description Xavi Hernandez 2014-10-24 11:55:30 UTC
+++ This bug was initially created as a clone of Bug #1156404 +++

Description of problem:

When trying to geo-replicate a dispersed volume, little after starting it, a 'gluster volume geo-replication ... status' shows all nodes as faulty and no data has been replicated.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-10-27 09:08:31 UTC
REVIEW: http://review.gluster.org/8976 (ec: Correctly handle xtime extended attribute) posted (#1) for review on release-3.6 by Xavier Hernandez (xhernandez)

Comment 2 Anand Avati 2014-10-28 08:40:06 UTC
COMMIT: http://review.gluster.org/8976 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit 5e9e6c1cc6933c886c8f8334ccee0cc76eb2fcb5
Author: Xavier Hernandez <xhernandez>
Date:   Fri Oct 24 15:03:12 2014 +0200

    ec: Correctly handle xtime extended attribute
    
    Change-Id: I2bd34f063d6bf1835d5ae57a8e9aa03f3ec3deb3
    BUG: 1156405
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: http://review.gluster.org/8976
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>

Comment 3 Niels de Vos 2014-11-10 15:14:25 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