<div dir="ltr"><div><div>IIUC, you would essentially be unmounting the volume from the old building and mounting it near the new building, correct?<br>In that case, you would need to set the read-subvolume-index command line option appropriately when mounting again.<br>The selection of the new read child will not happen automatically.<br><br></div>HTH,<br></div>Krutika<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 4, 2016 at 5:59 PM, Yannick Perret <span dir="ltr">&lt;<a href="mailto:yannick.perret@liris.cnrs.fr" target="_blank">yannick.perret@liris.cnrs.fr</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF"><span class="">
    <div>Le 04/03/2016 13:12, Krutika Dhananjay
      a écrit :<br>
    </div>
    <blockquote type="cite">
      <div style="font-family:garamond,new york,times,serif;font-size:12pt;color:#000000">
        <div>You could configure read-subvolume for individual clients
          using the following mount option:<br>
        </div>
        <div><br>
        </div>
        <div>mount -t glusterfs -o
          &quot;xlator-option=*replicate*.read-subvolume-index=0&quot;
          &lt;hostname&gt;:/&lt;volname&gt; &lt;mountpoint&gt;<br>
        </div>
        <div><br>
        </div>
        <div>In the example above, 0 represents the zeroth child. If a
          particular client wants to use the second brick as the read
          child, use the following:<br>
        </div>
        <div><br>
        </div>
        <div>mount -t glusterfs -o
          &quot;xlator-option=*replicate*.read-subvolume-index=1&quot;
          &lt;hostname&gt;:/&lt;volname&gt; &lt;mountpoint&gt;</div>
        <div><br>
        </div>
      </div>
    </blockquote></span>
    Thanks for that tip!<br>
    Just a question: as our clients can migrate beetween buildings (not
    often, but it happens), does using something like &#39;mount -o
    &quot;remount,xlator-option=*replicate*.read-subvolume-index=X&quot; …&#39; will
    allow the client to point to the new target without stopping volume
    availability for clients?<br>
    <br>
    --<br>
    Y.<span class=""><br>
    <blockquote type="cite">
      <div style="font-family:garamond,new york,times,serif;font-size:12pt;color:#000000">
        <div>-Krutika<br>
        </div>
        <hr>
        <blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From:
          </b>&quot;Yannick Perret&quot; <a href="mailto:yannick.perret@liris.cnrs.fr" target="_blank">&lt;yannick.perret@liris.cnrs.fr&gt;</a><br>
          <b>To: </b>&quot;Krutika Dhananjay&quot; <a href="mailto:kdhananj@redhat.com" target="_blank">&lt;kdhananj@redhat.com&gt;</a><br>
          <b>Cc: </b><a href="mailto:gluster-users@gluster.org" target="_blank">gluster-users@gluster.org</a><br>
          <b>Sent: </b>Friday, March 4, 2016 3:35:57 PM<br>
          <b>Subject: </b>Re: [Gluster-users] Per-client prefered
          server?<br>
          <div><br>
          </div>
        </blockquote>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
  </span></div>

</blockquote></div><br></div>