Bug 1379370

Summary:	Linkto file still exists on subvolumes even after the file is removed from mount point
Product:	Red Hat Gluster Storage	Reporter:	Prasad Desala <tdesala>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED WONTFIX	QA Contact:	Prasad Desala <tdesala>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	rhs-bugs, storage-qa-internal, tdesala
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-07 16:04:43 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:

Description Prasad Desala 2016-09-26 13:38:28 UTC

Description of problem:
=======================
Identified hashed sub-volumes (DHT specific link file) for the file and brought down those bricks by killing process on those servers. 
From mount point, removed the file and sent a lookup. The file has been removed from cached sub-volumes but Linkto file still exists on hashed subvolumes.
Brought up all the bricks that were killed and lookup was sent and still the Linkto file is still present on hashed subvols.

Version-Release number of selected component (if applicable):
=============================================================
3.8.4-1.el7.x86_64

Steps to reproduce:
===================
1) Create a distributed replica volume and start it.
2) FUSE mount the volume.
3) Create a file, lets say touch file_remove.
4) Rename file_remove such that the renamed file has DHT specific link file on different sub-volume than actual file. Lets say it was renamed to file_remove_rename_1.
5) Identify the hashed sub-volumes (DHT specific link file) and bring down those bricks by killing process on those servers.
6) Remove the file from mountpoint by issuing rm <renamed_filename>.
7) Send a lookup and check for the file on subvolumes, the file is not listed on cached subvolume but will be listed on hashed subvolumes.
8) Bring up all the bricks that were killed.
9) Send a lookup, Linkto file is still being seen on hashed subvolumes.

Actual results:
================
Linkto file still exists on subvolumes even after the file is removed from mount point

Expected results:
==============
Linkto file should not be seen on subvolumes as the file was removed from mountpoint.

Additional info:
===========