Bug 1029506

Summary:	AFR: “volume heal newvolume full” recover file -- deleted file not copy from carbon node
Product:	[Community] GlusterFS	Reporter:	huangchongyuan <huang.chongyuan.1989>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.4.1	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-03 08:54:52 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 huangchongyuan 2013-11-12 14:00:11 UTC

Description of problem:
AFR volume: create a AFR volume, and then change a file in one brick (just add a row, so it is a wrong file).I delete this wrong file in this brick, and then execute "gluster volume heal afr_full". Guess what? yes,it recover a file in this brick, but ... this file is a wrong file(changed by me),not a copy from carbon node. why ? 

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

How reproducible:
always and I have test many times

Steps to Reproduce:
1.create a AFR volume : afr_vol
2.change a file in one brick (just add a row)
3.gluster volume heal afr_vol full
4.recover a file (changed by me,not a copy from carbon node)

Actual results:
this file is the file which changed by me

Expected results:
recover a normal file (copy from other node)

Additional info:
so why?

Comment 1 Pranith Kumar K 2014-01-03 08:54:52 UTC

Files on bricks should not be modified directly. Marking this as not a bug