Bug 1223306

Summary:	gluster volume heal info shows stale entries
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Bhaskarakiran <byarlaga>
Component:	disperse	Assignee:	Ashish Pandey <aspandey>
Status:	CLOSED WORKSFORME	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	amukherj, aspandey, asriram, atumball, mzywusko, pkarampu, rhs-bugs, sankarshan, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	gluster volume heal <volname> info shows stale entries, even after the file is deleted. This happens due to rare cases when the gfid-handle of the file is not deleted. Workaround: On the bricks where the stale entries are present, for example, <gfid:5848899c-b6da-41d0-95f4-64ac85c87d3f>, perform the following steps: 1) Check if the file's gfid handle is not deleted. # find <brick-path>/.glusterfs -type f -links 1 and check if the file <brick-path>/.glusterfs/58/48/5848899c-b6da-41d0-95f4-64ac85c87d3f appears in the output. 2) If it appears in the output, you must delete that file. # rm <brick-path>/.glusterfs/58/48/5848899c-b6da-41d0-95f4-64ac85c87d3f	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-09 08:40:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1223636

Description Bhaskarakiran 2015-05-20 09:56:52 UTC

Description of problem:
=======================
created 1x(8+4) volume, fuse mounted on the client and created files and directories. During IO, brought down two of the bricks for some time and brough them back up. Let the IO finish and trigger heal full command. After some time, deleted all the entries from the client mount. With the heal info command, it still lists the gfid's though no entries are present on the mount.

Version-Release number of selected component (if applicable):
=============================================================
[root@transformers ~]# gluster --version
glusterfs 3.7.0 built on May 15 2015 01:31:12
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
[root@transformers ~]# 

How reproducible:
=================
most of the times

Steps to Reproduce:
1. Create 1x(8+4) disperse volume, Fuse mount on the client
2. create files and directories, untar linux kernel into multiple directories
3. Bring down 2 of the bricks. 
4. Wait for 10 mins and bring back the bricks with gluster v start force
5. Let the IO complete.
6. Trigger full heal with gluster v heal vol full
7. Delete all the data from the client mount
8. List with gluster v heal info command

Actual results:
===============
stale entries listed with gluster v heal info

Expected results:
=================
stale entries should get deleted

Additional info:
sosreports will be attached.

Comment 3 Anjana Suparna Sriram 2015-07-27 09:44:27 UTC

Please review and sign off to be included in the Known Issues chapter

Comment 4 Pranith Kumar K 2015-07-27 09:48:22 UTC

Looks good to me Anjana.