<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 10/7/2014 1:56 PM, Ryan Nix wrote:<br>
    <blockquote
cite="mid:CAOpa8k=yPfJ4FwVs_efE4e_Rvf5zu7bP+Vt494w929On3bRMSg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">Hello,
        <div><br>
        </div>
        <div>I seem to have hosed my installation while trying to
          replace a failed brick.  The instructions for replacing the
          brick with a different host name/IP on the Gluster site are no
          longer available so I used the instructions from the Redhat
          Storage class that I attended last week, which assumed the
          replacement had the same host name.</div>
        <div><br>
        </div>
        <div><a moz-do-not-send="true"
href="http://community.gluster.org/q/a-replica-node-has-failed-completely-and-must-be-replaced-with-new-empty-hardware-how-do-i-add-the-new-hardware-and-bricks-back-into-the-replica-pair-and-begin-the-healing-process/">http://community.gluster.org/q/a-replica-node-has-failed-completely-and-must-be-replaced-with-new-empty-hardware-how-do-i-add-the-new-hardware-and-bricks-back-into-the-replica-pair-and-begin-the-healing-process/</a><br>
        </div>
        <div><br>
        </div>
        <div>It seems the working brick (I had two servers with simple
          replication only) will not release the DNS entry of the failed
          brick.</div>
        <div><br>
        </div>
        <div>Is there any way to simply reset Gluster completely?</div>
      </div>
    </blockquote>
    The simple way to "reset gluster completely" would be to delete the
    volume and start over.  Sometimes this is the quickest way,
    especially if you only have one or two volumes.<br>
    <br>
    If nothing has changed, deleting the volume will not affect the data
    on the brick.<br>
    <br>
    You can either:<br>
    Find and follow the instructions to delete the "markers" that
    glusterfs puts on the brick, in which case the create process should
    be the same as any new volume creation.<br>
    Otherwise, when you do the "volume create..." step, it will give you
    an error, something like 'brick already in use'.  You used to be
    able to override that by adding --force to the command line.  (Have
    not needed it lately, so don't know if it still works.)<br>
    <br>
    Hope this helps<br>
    Ted Miller<br>
    Elkhart, IN<br>
    <blockquote
cite="mid:CAOpa8k=yPfJ4FwVs_efE4e_Rvf5zu7bP+Vt494w929On3bRMSg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>  </div>
        <div><br>
        </div>
        <div>Just to confirm, if I delete the volume so I can start
          over, deleting the volume will not delete the data.  Is this
          correct?  Finally, once the volume is deleted, do I have to do
          what Joe Julian recommended here? <a moz-do-not-send="true"
href="http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/">http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/</a></div>
        <div><br>
        </div>
        <div>Thanks for any insights.</div>
        <div><br>
        </div>
        <div>- Ryan</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://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
    </blockquote>
    <br>
  </body>
</html>