Bug 1119774
Summary: | background meta-data data missing-entry self-heal failed | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Hitesh <hitzimpossible> |
Component: | replicate | Assignee: | Pranith Kumar K <pkarampu> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.2 | CC: | bugs, gluster-bugs, pkarampu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-07 13:50:53 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
Hitesh
2014-07-15 13:23:10 UTC
Seems like there is a gfid-mismatch i.e there is an entry split-brain. i.e. same name with different gfids. Could you please follow instructions at https://github.com/gluster/glusterfs/blob/master/doc/split-brain.md to fix the issue. What the setup you have is entry-split-brain which is the final topic in that document. It would be nice to figure out how the system ended up in this situation. Could you please let us know what lead to this situation in your setup? Currently the lab is recovered but I had checked split-brain condition on the lab. There wasn't any split-brain entry. These are different kind of split-brains: Here is the log from the bug description you gave, which suggests that such a thing would have happened. [2014-07-08 09:14:07.892573] W [afr-common.c:1505:afr_conflicting_iattrs] 0-_tftpboot-replicate-0: /cnp/atcaf125/0-0-6-0/boarddata/etc/fstab: gfid differs on subvolume 0 GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed. GlusterFS 3.4.x has reached end-of-life.\ \ If this bug still exists in a later release please reopen this and change the version or open a new bug. |