[Bugs] [Bug 1568521] New: shard files present even after deleting vm from the rhev

[bugzilla at redhat.com]

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

            Bug ID: 1568521
           Summary: shard files present even after deleting vm from the
                    rhev
           Product: GlusterFS
           Version: mainline
         Component: sharding
          Keywords: Triaged
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: kdhananj at redhat.com
        QA Contact: bugs at gluster.org
                CC: abhishku at redhat.com, bugs at gluster.org,
                    kdhananj at redhat.com, rhinduja at redhat.com,
                    rhs-bugs at redhat.com, sasundar at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1520882
            Blocks: 1503138, 1522624



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

Description of problem:

ghost shard files present even after deleting vm from the rhev resulting more
space utilized than it should actually have.

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

glusterfs-3.8.4-18.6.el7rhgs.x86_64 

Actual results:

shard files available even after deleting vm

Expected results:

shard files should have deleted after vm deletion.

--- Additional comment from Abhishek Kumar on 2017-12-05 07:11:29 EST ---

Root cause of the issue :

Presence of 3 orphaned shard set in .shard location caused less free available
space on the volume.

All these 3 shard set almost consist of around 630 GB of space.

Reason for these shard not getting deleted after VM got deleted :
~~~
[2017-11-20 11:52:48.788824] W [fuse-bridge.c:1355:fuse_unlink_cbk]
0-glusterfs-fuse: 1725: UNLINK()
/1d7b3d24-88d4-4eba-a0cf-9bd3625acbf6/images/_remove_me_d9a3fbce-1abf-46b4-ab88-ae38a61bb9f9/e47a4bfe-84d8-4f29-af78-7730e7ec1008
=> -1 (Transport endpoint is not connected)
~~~
and a lot of errors of the kind 'Transport endpoint is not connected' in the
fuse mount log from both the replicas, it is clear that the UNLINK operation
(which is nothing but disk deletion) failed midway before all shards could be
cleaned up.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1520882
[Bug 1520882] [GSS]shard files present even after deleting vm from the rhev
https://bugzilla.redhat.com/show_bug.cgi?id=1522624
[Bug 1522624] [GSS]shard files present even after deleting vm from the rhev
-- 
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.