[Bugs] [Bug 1258334] Sharding - Unlink of VM images can sometimes fail with EINVAL

[bugzilla at redhat.com]

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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/12059 committed in master by Vijay Bellur
(vbellur at redhat.com) 
------
commit 7566c94633b602156755297493fad1d24d1ba52f
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date:   Mon Aug 31 12:43:36 2015 +0530

    features/shard: Fix unlink failure due to non-existent shard(s)

    Unlink of a sharded file with holes was leading to EINVAL errors
    because it was being wound on non-existent shards (those blocks that
    fall in the hole region). loc->inode was NULL in these cases and
    dht_unlink used to fail the FOP with EINVAL for failure to fetch
    cached subvol for the inode.

    The fix involves winding unlink on only those shards whose corresponding
    inodes exist in memory.

    Change-Id: I993ff70cab4b22580c772a9c74fc19ac893a03fc
    BUG: 1258334
    Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
    Reviewed-on: http://review.gluster.org/12059
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur 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.