Bug 1398829 - gluster can't heal the gfid mismatch file, suggest to heal with the new one.
Summary: gluster can't heal the gfid mismatch file, suggest to heal with the new one.
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: selfheal
Version: 3.6.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-26 14:06 UTC by lideqian
Modified: 2019-10-23 02:53 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-02 06:41:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.