<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 11/16/2017 12:54 PM, Daniel Berteaud
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:696b0d08-3679-a820-bfef-140d87c3856f@firewall-services.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      Le 15/11/2017 à 09:45, Ravishankar N a écrit :<br>
      <blockquote type="cite"
        cite="mid:dcf93f1d-62e9-d66d-65b4-c6b25ae32557@redhat.com">
        <meta http-equiv="Content-Type" content="text/html;
          charset=utf-8">
        If it is only the brick that is faulty on the bad node, but
        everything else is fine, like glusterd running, the node being a
        part of the trusted storage pool etc,  you could just kill the
        brick first and do step-13 in "10.6.2. Replacing a Host Machine
        with the Same Hostname", (the mkdir of non-existent dir,
        followed by setfattr of non-existent key) of <a
          class="moz-txt-link-freetext"
href="https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/pdf/Administration_Guide/Red_Hat_Storage-3.1-Administration_Guide-en-US.pdf"
          moz-do-not-send="true">https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/pdf/Administration_Guide/Red_Hat_Storage-3.1-Administration_Guide-en-US.pdf</a>,
        then restart the brick by restarting glusterd on that node. Read
        10.5 and 10.6 sections in the doc to get a better understanding
        of replacing bricks.<br>
      </blockquote>
      <br>
      Thanks, I'll try that.<br>
      Any way in this situation to check which file will be healed from
      which brick before reconnecting ? Using some getfattr tricks ?<br>
    </blockquote>
    Yes, there are afr xattrs that determine the heal direction for each
    file. The good copy will have non-zero trusted.afr* xattrs that
    blame the bad one and heal will happen from good to bad.  If both
    bricks have attrs blaming the other, then the file is in
    split-brain.<br>
    -Ravi<br>
    <blockquote type="cite"
      cite="mid:696b0d08-3679-a820-bfef-140d87c3856f@firewall-services.com"><br>
      Regards, Daniel<br>
      <br>
      <div class="moz-signature">-- <br>
        <meta http-equiv="Content-Type" content="text/html;
          charset=utf-8">
        <table>
          <tbody>
            <tr>
              <td>
                <p> <img
src="http://www.firewall-services.com/media/image/signature_mail_fws.png"
                    alt="Logo FWS" moz-do-not-send="true" width="275"> </p>
              </td>
              <td> <font size="2" face="Verdana, Geneva, sans-serif"> <strong>Daniel
                    Berteaud</strong><br>
                  <br>
                  FIREWALL-SERVICES SAS.<br>
                  Société de Services en Logiciels Libres<br>
                  Tel : <a
style="color:#00001f;background-color:#ffffdf;-moz-border-radius:3px;cursor:pointer"
                    title="Utiliser comme numéro" class="telified"
                    pattcc="+33" nr="0556641532" href="tel:0556641532"
                    moz-do-not-send="true">05 56 64 15 32</a><br>
                  Matrix: @dani:fws.fr<br>
                  <em><a class="moz-txt-link-abbreviated"
                      href="http://www.firewall-services.com"
                      moz-do-not-send="true">www.firewall-services.com</a></em>
                </font> </td>
            </tr>
          </tbody>
        </table>
      </div>
    </blockquote>
    <br>
  </body>
</html>