[Bugs] [Bug 1293584] Corrupted objects list does not get cleared even after all the files in the volume are deleted and count increases as old + new count

bugzilla at redhat.com bugzilla at redhat.com
Sat Jan 9 09:57:43 UTC 2016


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



--- Comment #7 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13032 committed in release-3.7 by Venky
Shankar (vshankar at redhat.com) 
------
commit 0f251fd517d2ed67330e11d56e9e64cca8390b35
Author: Raghavendra Bhat <raghavendra at redhat.com>
Date:   Wed Nov 25 15:25:26 2015 +0530

    features/bit-rot-stub: delete the link for bad object in quarantine
directory

    When the bad object is deleted (as of now manually from the backend
itself),
    along with its gfid handle, the entry for the bad object in the quarantne
    directory is left as it is (it also can be removed manually though). But
the
    next lookup of the object upon not finding it in the backend, sends forget
on
    the in-memory inode. If the stale link for the gfid still exists in the
    quarantine directory, bir-rot-stub will unlink the entry in its forget or
in
    the next failed lookup on that object with errno being ENOENT.

    Change-Id: If84292d3e44707dfa11fa29023b3d9f691b8f0f3
    BUG: 1293584
    Signed-off-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-on: http://review.gluster.org/12743
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>
    (cherry picked from commit f853ed9c61bf65cb39f859470a8ffe8973818868)
    Reviewed-on: http://review.gluster.org/13032

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


More information about the Bugs mailing list