[Bugs] [Bug 1434000] New: split-brain observed. [input/output error]

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1434000

            Bug ID: 1434000
           Summary: split-brain observed. [input/output error]
           Product: GlusterFS
           Version: 3.8
         Component: bitrot
          Assignee: bugs at gluster.org
          Reporter: 1linuxengineer at gmail.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem: the volume logfile reports a possible split-brain but
when I try to heal it fails because the file is not in split-brain


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


How reproducible:don't know


Steps to Reproduce:
1.
2.
3.

Actual results:affected files are not accessible, I/O error


Expected results:files fully accessible


Additional info:I don't know how we got into this situation. we have 2 machines
with 60 disks each. 42 of them are in 42 replicated gluster volumes. the
machines are running several lxc and the gluster volumes are presented into the
containers. the machines are under high memory pressure, so it could be that at
some point in time a critical process was killed by the OOM Killer.

root at chastcvtprd04:~# uname -a
Linux chastcvtprd04 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
root at chastcvtprd04:~# dpkg -l | grep gluster
ii  glusterfs-client                    3.8.8-ubuntu1~xenial1             
amd64        clustered file-system (client package)
ii  glusterfs-common                    3.8.8-ubuntu1~xenial1             
amd64        GlusterFS common libraries and translator modules
ii  glusterfs-server                    3.8.8-ubuntu1~xenial1             
amd64        clustered file-system (server package)


I have about 4GB of logs on my machines. Let me know what you need and I'll
upload it

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.