[Bugs] [Bug 1282388] Data Tiering:delete command rm -rf not deleting files the linkto file(hashed) which are under migration and possible spit-brain observed and possible disk wastage

bugzilla at redhat.com bugzilla at redhat.com
Mon Feb 22 14:50:59 UTC 2016


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



--- Comment #8 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12991 committed in release-3.7 by Dan
Lambright (dlambrig at redhat.com) 
------
commit 6a565219fb1631e9b14c676458c8c04251886494
Author: Mohammed Rafi KC <rkavunga at redhat.com>
Date:   Mon Nov 30 19:02:54 2015 +0530

    tier:unlink during migration

    files deleted during promotion were not deleting as the
    files are moving from hashed to non-hashed

    On deleting a file that is undergoing promotion,
    the unlink call is not sent to the dst file as the
    hashed subvol == cached subvol. This causes
    the file to reappear once the migration is complete.

    This patch also fixes a problem with stale linkfile
    deleting.

    Backport of>
    >Change-Id: I4b02a498218c9d8eeaa4556fa4219e91e7fa71e5
    >BUG: 1282390
    >Signed-off-by: Mohammed Rafi KC <rkavunga at redhat.com>
    >Reviewed-on: http://review.gluster.org/12829
    >Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    >Tested-by: 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 b5de382afa8c5777e455c7a376fc4f1f01d782d1)

    Change-Id: I951adb4d929926bcd646dd7574f7a2d41d57479d
    BUG: 1282388
    Signed-off-by: Mohammed Rafi KC <rkavunga at redhat.com>
    Reviewed-on: http://review.gluster.org/12991
    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>

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


More information about the Bugs mailing list