Re: [Gluster-users] Failed to mount nfs due to split-brain and Input/Output Error

2018-07-04 Thread Anh Vo
Output of glfsheal-gv0.log: [2018-07-04 16:11:05.435680] I [MSGID: 114035] [client-handshake.c:202:client_set_lk_version_cbk] 0-gv0-client-1: Server lk version = 1 [2018-07-04 16:11:05.436847] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 0-gv0-client-2: changing port to 49153 (from 0) [2018-07-04

Re: [Gluster-users] Failed to mount nfs due to split-brain and Input/Output Error

2018-07-04 Thread Ravishankar N
On 07/04/2018 09:20 PM, Anh Vo wrote: I forgot to mention we're using 3.12.10 On Wed, Jul 4, 2018 at 8:45 AM, Anh Vo > wrote: If I run "sudo gluster volume heal gv0 split-brain latest-mtime /" I get the following: Lookup failed on /:Invalid argument.

Re: [Gluster-users] Failed to mount nfs due to split-brain and Input/Output Error

2018-07-04 Thread Anh Vo
I forgot to mention we're using 3.12.10 On Wed, Jul 4, 2018 at 8:45 AM, Anh Vo wrote: > If I run "sudo gluster volume heal gv0 split-brain latest-mtime /" I get > the following: > > Lookup failed on /:Invalid argument. > Volume heal failed. > > node2 was not connected at that time, because if

Re: [Gluster-users] Failed to mount nfs due to split-brain and Input/Output Error

2018-07-04 Thread Anh Vo
If I run "sudo gluster volume heal gv0 split-brain latest-mtime /" I get the following: Lookup failed on /:Invalid argument. Volume heal failed. node2 was not connected at that time, because if we connect it to the system after a few minutes gluster will become almost unusable and we have many

Re: [Gluster-users] Failed to mount nfs due to split-brain and Input/Output Error

2018-07-03 Thread Ravishankar N
Hi, What version of gluster are you using? 1. The afr xattrs on '/' indicate a meta-data split-brain. You can resolve it using one of the policies listed in https://docs.gluster.org/en/latest/Troubleshooting/resolving-splitbrain/ For example, "|gluster volume heal gv0 split-brain

Re: [Gluster-users] Failed to mount nfs due to split-brain and Input/Output Error

2018-07-03 Thread Anh Vo
Actually we just discovered that the heal info command was returning different things when executed on the different nodes of our 3-replica setup. When we execute it on node2 we did not see the split brain reported "/" but if I execute it on node0 and node1 I am seeing: x@gfs-vm001:~$ sudo