Description of problem: With new trash translator, geo-rep goes to faulty trying to sync .trashcan. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. Create geo-replication session between master and slave 2. Start geo-replication 3. Actual results: Geo-rep goes to faulty. Expected results: Geo-rep should not goes to faulty Additional info:
REVIEW: http://review.gluster.org/9934 (geo-rep: Ignore .trashcan during xsync crawl.) posted (#1) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/9934 committed in master by Vijay Bellur (vbellur) ------ commit 2bf23b5b9be9ad600d71474a8f94b62765344b7c Author: Kotresh HR <khiremat> Date: Wed Mar 18 19:50:03 2015 +0530 geo-rep: Ignore .trashcan during xsync crawl. With trash feature, .trashcan directory gets created at each export directory. Xsync picks .trashcan to sync and fails with EPERM. Xsync should ignore .trashcan directory. Change-Id: I45bd226c96011ace2c40dd2de878d886c7d34ce5 BUG: 1203293 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/9934 Reviewed-by: Vijay Bellur <vbellur> Reviewed-by: Aravinda VK <avishwan> Reviewed-by: Venky Shankar <vshankar> Tested-by: Gluster Build System <jenkins.com>
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.7.0, please open a new bug report. glusterfs-3.7.0 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/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user