<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Thanks very much!  <br>
    </p>
    <p>Did that then recovered the ID as well using the below off of
      google:</p>
    <p>vol=mdsglusterv01<br>
      brick=/mnt/p01-d01/glusterv01<br>
      setfattr -n trusted.glusterfs.volume-id \<br>
        -v 0x$(grep volume-id /var/lib/glusterd/vols/$vol/info \<br>
        | cut -d= -f2 | sed 's/-//g') $brick<br>
      <br>
    </p>
    <p>Another question I had is, if I add a 2TB LUN brick to gluster,
      w/ the LUN existing on this physical node where I also have KVM
      running, will the KVM guests write directly to the LUN @ FC speeds
      or would the writes occur via glusterfs and the transport I
      selected below?   Is gluster intelligent enough to recognize that
      a particular brick exists on the same physical from which writes
      are occurring and allow direct writes to the brick via what ever
      medium it's mounted on (NFS, FC, FCoE, iSCSI etc)?  <br>
    </p>
    <p>Disk /dev/sdb: 2199.0 GB, 2199023255552 bytes, 4294967296 sectors</p>
    <p>[root@mdskvm-p01 ~]# gluster volume info<br>
      <br>
      Volume Name: mdsglusterv01<br>
      Type: Distribute<br>
      Volume ID: 84df37b3-3c68-4cc0-9383-3ff539a4d785<br>
      Status: Started<br>
      Number of Bricks: 1<br>
      Transport-type: tcp,rdma<br>
      Bricks:<br>
      Brick1: mdskvm-p01:/mnt/p01-d01/glusterv01<br>
      Options Reconfigured:<br>
      config.transport: tcp,rdma<br>
      performance.readdir-ahead: on<br>
      [root@mdskvm-p01 ~]#<br>
    </p>
    <div class="moz-signature">Cheers,<br>
      Tom K.<br>
-------------------------------------------------------------------------------------
      <br>
      Living on earth is expensive, but it includes a free trip around
      the sun.<br>
      <br>
    </div>
    <div class="moz-cite-prefix">On 5/2/2016 10:17 PM, Chen Chen wrote:<br>
    </div>
    <blockquote
      cite="mid:13f21bf6-8cb8-a949-7fdf-686dfd4513a1@smartquerier.com"
      type="cite">Hi Tom,
      <br>
      <br>
      You may try:
      <br>
      gluster volume set volname config.transport tcp
      <br>
      <br>
      ref:
      <br>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/community/documentation/index.php/RDMA_Transport#Changing_Transport_of_Volume">http://www.gluster.org/community/documentation/index.php/RDMA_Transport#Changing_Transport_of_Volume</a>
      <br>
      <br>
      Best regards,
      <br>
      Chen
      <br>
      <br>
      On 5/3/2016 9:55 AM, TomK wrote:
      <br>
      <blockquote type="cite">Hey All,
        <br>
        <br>
        New here and first time posting.  I've made a typo in
        configuration and
        <br>
        entered:
        <br>
        <br>
        gluster volume create mdsglusterv01 transport rdma
        <br>
        mdskvm-p01:/mnt/p01-d01/glusterv01/
        <br>
        <br>
        but couldn't start since rdma didn't exist:
        <br>
        <br>
        [root@mdskvm-p01 glusterfs]# ls -altri
        <br>
        /usr/lib64/glusterfs/3.7.11/rpc-transport/*
        <br>
        135169384 -rwxr-xr-x. 1 root root 99648 Apr 18 08:21
        <br>
        /usr/lib64/glusterfs/3.7.11/rpc-transport/socket.so
        <br>
        [root@mdskvm-p01 glusterfs]#
        <br>
        <br>
        So how do I reconfigure gluster to remove the rdma option and
        redefine
        <br>
        this brick?
        <br>
        <br>
        [root@mdskvm-p01 glusterfs]# gluster volume info
        <br>
        <br>
        Volume Name: mdsglusterv01
        <br>
        Type: Distribute
        <br>
        Volume ID: 84df37b3-3c68-4cc0-9383-3ff539a4d785
        <br>
        Status: Stopped
        <br>
        Number of Bricks: 1
        <br>
        Transport-type: rdma
        <br>
        Bricks:
        <br>
        Brick1: mdskvm-p01:/mnt/p01-d01/glusterv01
        <br>
        Options Reconfigured:
        <br>
        performance.readdir-ahead: on
        <br>
        [root@mdskvm-p01 glusterfs]#
        <br>
        <br>
        I figure I can add in a dummy block device however wanted to
        find out if
        <br>
        there's anyway to change the above or redefine it before I do
        that.
        <br>
        <br>
        Cheers,
        <br>
        Tom K.
        <br>
-------------------------------------------------------------------------------------
        <br>
        <br>
        Living on earth is expensive, but it includes a free trip around
        the sun.
        <br>
        <br>
        <br>
        <br>
        _______________________________________________
        <br>
        Gluster-users mailing list
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
        <br>
        <a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a>
        <br>
        <br>
      </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://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
    </blockquote>
    <br>
  </body>
</html>