[Bugs] [Bug 1458664] New: [Geo-rep]: METADATA errors are seen even though everything is in sync

bugzilla at redhat.com bugzilla at redhat.com
Mon Jun 5 07:18:28 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1458664

            Bug ID: 1458664
           Summary: [Geo-rep]: METADATA errors are seen even though
                    everything is in sync
           Product: GlusterFS
           Version: 3.11
         Component: geo-replication
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org, sarumuga at redhat.com
        Depends On: 1455559



+++ This bug was initially created as a clone of Bug #1455559 +++

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:

--- Additional comment from Worker Ant on 2017-05-25 09:09:26 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Ignore ENOENT while meta
data syncing) posted (#1) for review on master by Kotresh HR
(khiremat at redhat.com)

--- Additional comment from Worker Ant on 2017-05-31 05:15:13 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on
symlink) posted (#2) for review on master by Kotresh HR (khiremat at redhat.com)

--- Additional comment from Worker Ant on 2017-05-31 08:02:06 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on
symlink) posted (#3) for review on master by Kotresh HR (khiremat at redhat.com)

--- Additional comment from Kotresh HR on 2017-05-31 08:05:41 EDT ---



--- Additional comment from Worker Ant on 2017-06-02 08:10:42 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on
symlink) posted (#4) for review on master by Kotresh HR (khiremat at redhat.com)

--- Additional comment from Worker Ant on 2017-06-02 08:12:52 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on
symlink) posted (#5) for review on master by Kotresh HR (khiremat at redhat.com)

--- Additional comment from Worker Ant on 2017-06-02 08:16:27 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on
symlink) posted (#6) for review on master by Kotresh HR (khiremat at redhat.com)

--- Additional comment from Worker Ant on 2017-06-02 11:23:41 EDT ---

REVIEW: https://review.gluster.org/17389 (geo-rep: Fix meta data sync on
symlink) posted (#7) for review on master by Aravinda VK (avishwan at redhat.com)

--- Additional comment from Worker Ant on 2017-06-04 04:27:23 EDT ---

COMMIT: https://review.gluster.org/17389 committed in master by Aravinda VK
(avishwan at redhat.com) 
------
commit 324e81d6fea324d512431a2604086326b8848e9b
Author: Kotresh HR <khiremat at redhat.com>
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 at redhat.com>
    Reviewed-on: https://review.gluster.org/17389
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1455559
[Bug 1455559] [Geo-rep]: METADATA errors are seen even though everything is
in sync
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list