Bug 1038103

Summary:	Split-brain *.dat
Product:	[Community] GlusterFS	Reporter:	G K <gojkok>
Component:	fuse	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	bugs, 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:	2015-10-07 12:13:00 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 G K 2013-12-04 12:34:25 UTC

Description of problem: Only .dat files Split-brain problem.


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


How reproducible:Shutdown one brick of two from gluster.


Steps to Reproduce:
1.Shutdown one brick, and start it after one day
2.
3.

Actual results:
ls: cannot access /inbox/imapindex.dat: Input/output error
-?????????? ? ?    ?           ?            ? imapindex.dat

Expected results:
To work without any problem.

Additional info:
We have a power failure on one of the server that is brick in the gluster of two bricks. We are using that gluster as a storage for our mails. After one day we start that brick and after some time we notice that user cannot access their mails. After some inspection we notice that only .dat are inaccessible. We are using Icewarp mail server, and storage for mails are on separate servers that are run on the gluster.

Comment 1 Niels de Vos 2015-05-17 22:00:24 UTC

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.

Comment 2 Kaleb KEITHLEY 2015-10-07 12:13:00 UTC

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.