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 How reproducible: Customer environment Actual results: shard files available even after deleting vm Expected results: shard files should have deleted after vm deletion. Additional info:
https://review.gluster.org/c/glusterfs/+/20623 https://review.gluster.org/q/topic:%22ref-1568521%22+(status:open%20OR%20status:merged)
Updated Doctext field. Kindly review for technical accuracy.
(In reply to Anjana from comment #23) > Updated Doctext field. Kindly review for technical accuracy. Hi, The doc itself looks good. But I just wanted to highlight that this won't be a known issue once RHGS-3.4 Batch Update 2 is rolled out, which is where it is being fixed. My understanding is that if this doc text is going to make it to the "known issues" section of batch update 2, then this won't be necessary as it is going to be fixed there. -Krutika
Changed doc-type.
Changed the doc text in CCFR format. -Krutika
Verified with glusterfs-3.12.2-31.el7rhgs and RHV 4.2.7-1 1. Created a 2 TB disk on the gluster SD backed with 64MB sharded gluster volume 2. Created a filesystem on the disk and populated data almost around 2TB. 3. Deleted the VM image from RHV storage domain. Observed that there are no hangs, no issues with SD or hosts, all the shards are deleted. No ghost shards left behind.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3827