[Bugs] [Bug 1302979] [georep+tiering]: Hardlink sync is broken if master volume is tiered

[bugzilla at redhat.com]

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



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13315 committed in release-3.7 by Vijay
Bellur (vbellur at redhat.com) 
------
commit 478203fd9447cbc67c7cdc2980d6bdf4881984bf
Author: Saravanakumar Arumugam <sarumuga at redhat.com>
Date:   Fri Jan 22 16:58:13 2016 +0530

    geo-rep: Handle hardlink in Tiering based volume

    Problem:
    Hardlinks are synced as Sticky bit files to Slave in
    a Tiering based volume.
    In a Tiering based volume, cold tier is hashed subvolume
    and geo-rep captures all namespace operations in cold tier.

    While syncing a file and its corresponding hardlink, it is
    recorded as MKNOD in cold tier(for both) and
    We end up creating two different files in Slave.

    Solution:
    If MKNOD with Sticky bit set is present, record it as LINK.
    This way it will create a HARDLINK if source file exists (on slave),
    else it will create a new file.

    This way, Slave can create Hardlink file itself (instead
    of creating a new file) in case of hardlink.

    Change-Id: Ic50dc6e64df9ed01799c30539a33daace0abe6d4
    BUG: 1302979
    Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-on: http://review.gluster.org/13281
    Reviewed-on: http://review.gluster.org/13315
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.