Bug 1286198

Summary:	dht: for moving file inside a new directory it asks for "overwrite?"
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	kramdoss, mzywusko, nbalacha, rgowdapp, rhs-bugs, spalai, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	dht-rca-unknown, dht-rename-file
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1026375	Environment:
Last Closed:	2016-07-04 09:06:20 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:	1026375
Bug Blocks:

Comment 2 Raghavendra G 2016-07-04 09:06:20 UTC

Given the bug description, it seems like a rename vs lookup selfheal resulting in both src and dst having same gfid. When two different directories share the same gfid (say mv src dst), files in single "src" directory is split (or listed) in both src and dst directory as is seen in this bug. However, the bug doesn't really explain all the sequence of operations that led to dir3/dirn and dir to have same gfid. We suspect this test was carried out on a volume which has already gone into an inconsistent state (possibly due to scenarios as in bz 1118770).

I am closing this bug due to following reasons:
1. test was carried out on a volume which has already gone into an inconsistent state
2. The root cause issue of two directories having same gfid are being tracked by various other bugs (like bz 111870).

Please re-open if you don't feel the reasons are not compelling enough.

regards,
Raghavendra.