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

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/12061 committed in release-3.7 by Kaushal M
(kaushal at redhat.com) 
------
commit 300a69669aa6e9ebb16e5fc8326ac57c3e2d8937
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)

            Backport of: http://review.gluster.org/#/c/12059/

    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: I1e5d492a2e60491601da23f64a5d0089e536b305
    BUG: 1258353
    Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
    Reviewed-on: http://review.gluster.org/12061
    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>

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