Description of problem: Even though master and slave arequal checksum matches, METADATA errors are being logged in master with errno ENOENT. Version-Release number of selected component (if applicable): master How reproducible: Always Steps to Reproduce: 1. Setup geo-rep 2. Untar linux src on master and let it sync to slave Actual results: METADATA errors are logged in master with ENOENT Expected results: It should not be logged. Additional info:
REVIEW: https://review.gluster.org/17389 (geo-rep: Ignore ENOENT while meta data syncing) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#2) for review on master by Kotresh HR (khiremat)
REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#3) for review on master by Kotresh HR (khiremat)
*** Bug 1239109 has been marked as a duplicate of this bug. ***
REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#4) for review on master by Kotresh HR (khiremat)
REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#5) for review on master by Kotresh HR (khiremat)
REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#6) for review on master by Kotresh HR (khiremat)
REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on symlink) posted (#7) for review on master by Aravinda VK (avishwan)
COMMIT: https://review.gluster.org/17389 committed in master by Aravinda VK (avishwan) ------ commit 324e81d6fea324d512431a2604086326b8848e9b Author: Kotresh HR <khiremat> Date: Thu May 25 07:28:07 2017 -0400 geo-rep: Fix meta data sync on symlink chmod doesn't support 'no dereference' option. It always deference the symlink. But 'chown' does support metadata changes on symlink itself, which was not taken care while syncing. This patch fixes the same. Change-Id: Ic9985f4e39d15b5a9deb379841bcfb2c263d3e6c BUG: 1455559 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: https://review.gluster.org/17389 NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Aravinda VK <avishwan> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> CentOS-regression: Gluster Build System <jenkins.org>
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.12.0, please open a new bug report. glusterfs-3.12.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://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/