Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1398829

Summary:	gluster can't heal the gfid mismatch file, suggest to heal with the new one.
Product:	[Community] GlusterFS	Reporter:	lideqian <deqian.li>
Component:	selfheal	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.9	CC:	bugs, deqian.li
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-02 06:41:08 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:

Description lideqian 2016-11-26 14:06:50 UTC

Description of problem:
How to heal the gfid mismatch file?

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


How reproducible:
two replicate bricks, stop or remove one,and create a new file with the same name as the stop one, and start (add) back the brick, gfid mismatch happen. how to heal this automatically ? 

Steps to Reproduce:
1.stop one brick
2.remove then create a new file or use vi to edit one file
3.start the brick

Actual results:
gfid mismatch of the file

Expected results:
no gfid mismatch, can heal the file selfly (use the new file as source)

Additional info: N/A

Comment 1 Niels de Vos 2016-11-29 12:23:26 UTC

Sorry, glusterfs-3.6 is End-Of-Life and will not receive any updates anymore. Please see https://www.gluster.org/community/release-schedule/ for the current versions that still get updates. Please correct the version of this bug report. All 3.6 bugs will be closed in the near future.

Comment 2 hari gowtham 2016-12-02 06:41:08 UTC

This bug is getting closed because the 3.6 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.