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

[bugzilla at redhat.com]

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

            Bug ID: 1258353
           Summary: Sharding - Unlink of VM images can sometimes fail with
                    EINVAL
           Product: GlusterFS
           Version: 3.7.3
         Component: sharding
          Keywords: Triaged
          Severity: high
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: kdhananj at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org, pcuzner at redhat.com
        Depends On: 1258334



+++ This bug was initially created as a clone of Bug #1258334 +++

Description of problem:

Thanks to Paul Cuzner for reporting this issue.
rm -rf on VM images in sharded volumes sometimes fails with EINVAL.

rhev-data-center-mnt-glusterSD-gprfc085-glfs.rhev-rhss.lab:vmdomain.log:[2015-08-30
22:27:32.842940] W [fuse-bridge.c:1292:fuse_unlink_cbk] 0-glusterfs-fuse:
22544605: UNLINK()
/2ad90339-5c1b-4b0e-b728-3df651ecd025/images/_remouLgHrB/e39cb165-831a-46cb-88da-e26cc93d9399
=> -1 (Invalid argument)
rhev-data-center-mnt-glusterSD-gprfc085-glfs.rhev-rhss.lab:vmdomain.log:[2015-08-30
22:27:59.238742] W [fuse-bridge.c:1292:fuse_unlink_cbk] 0-glusterfs-fuse:
22545653: UNLINK()
/2ad90339-5c1b-4b0e-b728-3df651ecd025/images/_remotGxj4J/aaa115ea-7577-4358-856e-a0101b7b94a2
=> -1 (Invalid argument)

Turns out the bug is in shard_unlink_shards_do() wherein the loop that winds
unlinks on individual shards must check for the inode associated with every
shard to exist in memory (local->inode_list[]) before winding unlink on it.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1258334
[Bug 1258334] Sharding - Unlink of VM images can sometimes fail with EINVAL
-- 
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.