+++ 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:
REVIEW: http://review.gluster.org/8976 (ec: Correctly handle xtime extended attribute) posted (#1) for review on release-3.6 by Xavier Hernandez (xhernandez)
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>
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