Description of problem: During Hybrid Crawl, Last synced status shows wrong value.
Last synced status picks from internal markings of stime xattr while updating for directories. Last synced value to be shown only when it is updated in Brick root(not sub directories) Note: Last Synced Value will not change untill Hybrid crawl completes.
REVIEW: http://review.gluster.org/15869 (geo-rep: Fix Last synced status column issue during Hybrid Crawl) posted (#1) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/15869 committed in master by Aravinda VK (avishwan) ------ commit 1876454d2e7950f25d1e5bb8e2c07ab27d521498 Author: Aravinda VK <avishwan> Date: Thu Nov 17 17:47:29 2016 +0530 geo-rep: Fix Last synced status column issue during Hybrid Crawl During Hybrid crawl, Geo-rep maintains stime xattr in subdirectories along with the Brick root. This is done to skip directories if Geo-rep crashes before Hybrid crawl completes. Update Last synced status only when stime xattr updated in brick root. Status output will mislead if it shows sub directory stime as last synced time. BUG: 1396081 Change-Id: I5b73aee7ae4a1c1e2d1001d1f55559b9f9efd6e6 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/15869 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat>
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.10.0, please open a new bug report. glusterfs-3.10.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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/