Re: [Gluster-users] volume start: gv01: failed: Quorum not met. Volume operation not allowed.

On 4/11/2018 11:54 AM, Alex K wrote: Hey Guy's, Returning to this topic, after disabling the the quorum: cluster.quorum-type: none cluster.server-quorum-type: none I've ran into a number of gluster errors (see below). I'm using gluster as the backend for my NFS storage. I have gluster

Re: [Gluster-users] volume start: gv01: failed: Quorum not met. Volume operation not allowed.

On 4/11/2018 11:54 AM, Alex K wrote: Hey Guy's, Returning to this topic, after disabling the the quorum: cluster.quorum-type: none cluster.server-quorum-type: none I've ran into a number of gluster errors (see below). I'm using gluster as the backend for my NFS storage. I have gluster

Re: [Gluster-users] volume start: gv01: failed: Quorum not met. Volume operation not allowed.

On Wed, Apr 11, 2018 at 4:35 AM, TomK wrote: > On 4/9/2018 2:45 AM, Alex K wrote: > Hey Alex, > > With two nodes, the setup works but both sides go down when one node is > missing. Still I set the below two params to none and that solved my issue: > > cluster.quorum-type:

Re: [Gluster-users] volume start: gv01: failed: Quorum not met. Volume operation not allowed.

On 4/9/2018 2:45 AM, Alex K wrote: Hey Alex, With two nodes, the setup works but both sides go down when one node is missing. Still I set the below two params to none and that solved my issue: cluster.quorum-type: none cluster.server-quorum-type: none Thank you for that. Cheers, Tom Hi,

Re: [Gluster-users] volume start: gv01: failed: Quorum not met. Volume operation not allowed.

Hi, You need 3 nodes at least to have quorum enabled. In 2 node setup you need to disable quorum so as to be able to still use the volume when one of the nodes go down. On Mon, Apr 9, 2018, 09:02 TomK wrote: > Hey All, > > In a two node glusterfs setup, with one node down,

[Gluster-users] volume start: gv01: failed: Quorum not met. Volume operation not allowed.

Hey All, In a two node glusterfs setup, with one node down, can't use the second node to mount the volume. I understand this is expected behaviour? Anyway to allow the secondary node to function then replicate what changed to the first (primary) when it's back online? Or should I just go