[Bugs] [Bug 1476212] [geo-rep]: few of the self healed hardlinks on master did not sync to slave

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17907 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit a060485aae8cb508e05e0f9e46e3f0ec823a7f22
Author: Kotresh HR <khiremat at redhat.com>
Date:   Wed Jul 26 08:09:31 2017 -0400

    geo-rep: Fix syncing of self healed hardlinks

    Problem:
    In a distribute replicate volume, if the hardlinks
    are created when a subvolume is down, it gets
    healed from other subvolume when it comes up.
    If this subvolume becomes ACTIVE in geo-rep
    there are chances that those hardlinks won't
    be synced to slave.

    Cause:
    AFR can't detect hardlinks during self heal.
    It just create those files using mknod and
    the same is recorded in changelog. Geo-rep
    processes these mknod and ignores it as
    it finds gfid already on slave.

    Solution:
    Geo-rep should process the mknod as link
    if the gfid already exists on slave.

    > Change-Id: I2f721b462b38a74c60e1df261662db4b99b32057
    > BUG: 1475308
    > Signed-off-by: Kotresh HR <khiremat at redhat.com>
    > Reviewed-on: https://review.gluster.org/17880
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Aravinda VK <avishwan at redhat.com>
    (cherry picked from commit d685e4238fafba8f58bf01174c79cb5ca35203e5)


    Change-Id: I2f721b462b38a74c60e1df261662db4b99b32057
    BUG: 1476212
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: https://review.gluster.org/17907
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=uGPu4KAYMU&a=cc_unsubscribe