<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 05/22/2017 03:11 AM, W Kern wrote:<br>
    </div>
    <blockquote
      cite="mid:7a9bfbc2-09d7-8d3a-1190-992126bb6766@bneit.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <p>So I am experimenting with shards using a couple VMs and
        decided to test his scenario (i.e. only one node available on a
        simple 2 node + 1 arbiter replicated/sharded volume use 3.10.1
        on Cent7.3)<br>
      </p>
      <p>I setup a VM testbed. Then verified everything including the
        sharding works and then shutdown nodes 2 and 3 (the arbiter).</p>
      <p>As expected I got a quorum error on the mount.</p>
      <p>So I tried</p>
      <p>gluster volume set VOL cluster.quorum-type none</p>
      <p>from the remaining 'working' node1 and it simply responds with</p>
      <p>"volume set: failed: Quorum not met. Volume operation not
        allowed"</p>
      <p>how do you FORCE gluster to ignore the quorum in such a
        situation? <br>
      </p>
    </blockquote>
    You probably also have server quorum enabled
    (cluster.server-quorum-type = server). Server quorum enforcement
    does not allow modifying volume options or other actions like peer
    probing/detaching if server quorum is not met.<br>
    <br>
    Also, don't disable client quorum for arbiter volumes or you will
    end up corrupting the files. For instance, if the arbiter brick was
    the only one that is up, and you disabled client quorum, then a
    writev from the application will get a success but nothing will ever
    get written on-disk on the arbiter brick.<br>
    <br>
    -Ravi<br>
    <blockquote
      cite="mid:7a9bfbc2-09d7-8d3a-1190-992126bb6766@bneit.com"
      type="cite">
      <p> </p>
      I tried stopping the volume and even rebooting node1 and still get
      the error (And of course the volume wont start for the same
      reason)<br>
      <br>
      -WK<br>
      <br>
      <br>
      <div class="moz-cite-prefix">On 5/18/2017 7:41 AM, Ravishankar N
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:82f328b5-c06a-daa4-7902-45e4558e7609@redhat.com">
        <meta http-equiv="Context-Type" content="text/html;
          charset=utf-8">
        <div class="moz-cite-prefix">On 05/18/2017 07:18 PM, <a
            class="moz-txt-link-abbreviated"
            href="mailto:lemonnierk@ulrar.net" moz-do-not-send="true">lemonnierk@ulrar.net</a>
          wrote:<br>
        </div>
        <blockquote cite="mid:20170518134844.GB15404@kalry" type="cite">
          <pre wrap="">Hi,


We are having huge hardware issues (oh joy ..) with RAID cards.
On a replica 3 volume, we have 2 nodes down. Can we somehow tell
gluster that it's quorum is 1, to get some amount of service back
while we try to fix the other nodes or install new ones ?
</pre>
        </blockquote>
        If you know what you are getting into, then `gluster v set
        &lt;volname&gt; cluster.quorum-type none` should give you the
        desired result, i.e. allow write access to the volume.<br>
        <blockquote cite="mid:20170518134844.GB15404@kalry" type="cite">
          <pre wrap="">Thanks
</pre>
          <br>
          <fieldset class="mimeAttachmentHeader"></fieldset>
          <br>
          <pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org" moz-do-not-send="true">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/gluster-users" moz-do-not-send="true">http://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
        </blockquote>
        <p><br>
        </p>
        <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
          <table>
            <tbody>
              <tr>
                <td><a
href="http://www.avg.com/email-signature?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=emailclient"
                    target="_blank" moz-do-not-send="true"><img alt=""
                      moz-do-not-send="true" height="29" width="46"></a></td>
                <td>Virus-free. <a
href="http://www.avg.com/email-signature?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=emailclient"
                    target="_blank" moz-do-not-send="true">www.avg.com</a>
                </td>
              </tr>
            </tbody>
          </table>
          <a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
            height="1" moz-do-not-send="true"> </a></div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
Gluster-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/gluster-users">http://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/gluster-users">http://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>