[Bugs] [Bug 1311836] [Tier]: Endup in multiple entries of same file on client after rename which had a hardlinks

[bugzilla at redhat.com]

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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13517 committed in release-3.7 by Dan
Lambright (dlambrig at redhat.com) 
------
commit cf86db23169a47008d963a5fd608b7352b0ed0cc
Author: N Balachandran <nbalacha at redhat.com>
Date:   Thu Feb 25 12:53:07 2016 +0530

    cluster/tier: Create linkfiles to hardlinks correctly

    There is a bug in the way hardlinks are handled in tiered volumes.
    Ideally, the tier linkto files on the cold tier to files that are
    hardlinks to each other on the hot tier, should themselves be
    hardlinks of each other. As they are not, they end up being files
    with the same gfid but different names for the cold tier dht,
    and end up overwriting the cached-subvol information stored in the dht
inode-ctx.

    > Change-Id: Ic658a316836e6a1729cfea848b7d212674b0edd2
    > BUG: 1305277
    > Signed-off-by: N Balachandran <nbalacha at redhat.com>
    > Reviewed-on: http://review.gluster.org/13391
    > 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>
    > Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    > Tested-by: Dan Lambright <dlambrig at redhat.com>
    (cherry picked from commit eb362c74db84d95aac07febf0d888bd98b3fb2b9)

    Change-Id: I5dd98e6d248619147974a630d7d72e1942a1cc83
    BUG: 1311836
    Signed-off-by: N Balachandran <nbalacha at redhat.com>
    Reviewed-on: http://review.gluster.org/13517
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>

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