>>So in this case, although the volume status shows up that volume is not
>>started, the brick process(es) actually do start. As a workaround please use
>>volume start force one more time.
Thanks Atin for providing the bug info.
--
Deepak
> On Feb 25, 2017, at 7:16 AM, Atin Mukherjee wrote:
>
k1: storageN1:/gluster/disk1/home-folder
>
> Brick2: storageN2:/gluster/disk1/home-folder
>
> Options Reconfigured:
>
> performance.readdir-ahead: on
>
> nfs.disable: on
>
> root@hostname:~#
>
>
>
>
>
> --
>
> Deepak
>
>
>
>
>
> *
It looks like it is ended up in split brain kind of situation. To find
the root cause we need to get logs for the first failure of volume start
or volume stop .
Or to work around it, you can do a volume start force.
Regards
Rafi KC
On 02/24/2017 01:36 PM, Deepak Naidu wrote:
>
> I keep on get
I keep on getting this error when my config.transport is set to both tcp,rdma.
The volume doesn't start. I get the below error during volume start.
To get around this, I end up delete the volume, then configure either only rdma
or tcp. May be I am missing something, just trying to get the volume
