Bug 1399470
Summary: | Wrong value in Last Synced column during Hybrid Crawl | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Aravinda VK <avishwan> |
Component: | geo-replication | Assignee: | Aravinda VK <avishwan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.9 | CC: | bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.9.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1396081 | Environment: | |
Last Closed: | 2017-03-08 10:20:37 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: | 1396081 | ||
Bug Blocks: | 1397286 |
Description
Aravinda VK
2016-11-29 06:28:59 UTC
REVIEW: http://review.gluster.org/15962 (geo-rep: Fix Last synced status column issue during Hybrid Crawl) posted (#1) for review on release-3.9 by Aravinda VK (avishwan) COMMIT: http://review.gluster.org/15962 committed in release-3.9 by Aravinda VK (avishwan) ------ commit f1ef6b0c1e5d6f0f7eb67e85b3837c0cf33642c9 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. > 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> BUG: 1399470 Change-Id: I5b73aee7ae4a1c1e2d1001d1f55559b9f9efd6e6 Signed-off-by: Aravinda VK <avishwan> (cherry picked from commit 1876454d2e7950f25d1e5bb8e2c07ab27d521498) Reviewed-on: http://review.gluster.org/15962 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Saravanakumar Arumugam <sarumuga> 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.9.1, please open a new bug report. glusterfs-3.9.1 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-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/ |