<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 10/07/2015 12:06 AM, Lindsay
      Mathieson wrote:<br>
    </div>
    <blockquote
cite="mid:CAEMkAmGdEVQNDJy3EW52dC8rtH9OawuhzRHMZc-yRjzAe8j+YQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div>First up - one of the things that concerns
                          me re gluster is the incoherent state of
                          documentation. The only docs linked on the
                          main webpage are for 3.2 and there is almost
                          nothing on how to handle failure modes such as
                          dead disks/bricks etc, which is one of
                          glusters primary functions.<br>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Every link under Documentation at <a class="moz-txt-link-freetext" href="http://gluster.org">http://gluster.org</a> points to the
    gluster.readthedocs.org pages that are all current. Where is this
    "main webpage" in which you found links to the old wiki pages?<br>
    <br>
    <blockquote
cite="mid:CAEMkAmGdEVQNDJy3EW52dC8rtH9OawuhzRHMZc-yRjzAe8j+YQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div><br>
                        </div>
                        My problem - I have a replica 2 volume, 2 nodes,
                        2 bricks (zfs datasets).<br>
                        <br>
                      </div>
                      As a test, I destroyed one brick (zfs destroy the
                      dataset).<br>
                      <br>
                      <br>
                    </div>
                    Can't start the datastore1:<br>
                    <br>
                      volume start: datastore1: failed: Failed to find
                    brick directory /glusterdata/datastore1 for volume
                    datastore1. Reason : No such file or directory<br>
                    <br>
                  </div>
                  A bit disturbing, I was hoping it would work off the
                  remaining brick.<br>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    It <b>is</b> still working off the remaining brick. It won't start
    the missing brick because the missing brick is missing. This is by
    design. If, for whatever reason, your brick did not mount, you don't
    want gluster to start filling your root device with replication from
    the other brick.<br>
    <br>
    I documented this on my blog at
    <a class="moz-txt-link-freetext" href="https://joejulian.name/blog/replacing-a-brick-on-glusterfs-340/">https://joejulian.name/blog/replacing-a-brick-on-glusterfs-340/</a>
    which is still accurate for the latest version.<br>
    <br>
    The bug report I filed for this was closed without resolution. I
    assume there's no plans for ever making this easy for
    administrators.<br>
    <a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=991084">https://bugzilla.redhat.com/show_bug.cgi?id=991084</a><br>
    <br>
    <blockquote
cite="mid:CAEMkAmGdEVQNDJy3EW52dC8rtH9OawuhzRHMZc-yRjzAe8j+YQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>Can't replace the brick:<br>
                <br>
                  gluster volume replace-brick datastore1
                vnb.proxmox.softlog:/glusterdata/datastore1
                vnb.proxmox.softlog:/glusterdata/datastore1-2 commit
                force<br>
                <br>
              </div>
              because the store is not running.<br>
              <br>
            </div>
            <div>After a lot of googling I found list messages
              referencing the remove brick command:<br>
            </div>
            gluster volume remove-brick datastore1 replica 2
            vnb.proxmox.softlog:/glusterdata/datastore1c commit force<br>
            <br>
          </div>
          Fails with the unhelpful error:<br>
          <br>
          wrong brick type: commit, use
          &lt;HOSTNAME&gt;:&lt;export-dir-abs-path&gt;<br>
          Usage: volume remove-brick &lt;VOLNAME&gt; [replica
          &lt;COUNT&gt;] &lt;BRICK&gt; ...
          &lt;start|stop|status|commit|force&gt;<br>
          <br>
        </div>
        In the end I destroyed and recreated the volume so I could
        resume testing, but I have no idea how I would handle a real
        failed brick in the future<br clear="all">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div>
                          <div><br>
                            -- <br>
                            <div class="gmail_signature">Lindsay</div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <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://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
    </blockquote>
    <br>
  </body>
</html>