OK, thanks! I will try that. .. Lana (lana.deere at gmail.com) On Wed, Dec 8, 2010 at 6:47 PM, Craig Carl <craig at gluster.com> wrote: > Lana - > ? That is a documentation bug, I have fixed it. There isn't a way to change > the transport type on an existing volume, but if you delete the volume then > recreate it exactly the same way with a different transport type it will > work fine. > > Thanks, > > Craig > > --> > Craig Carl > Senior Systems Engineer > Gluster > > On 12/08/2010 08:01 AM, Lana Deere wrote: >> >> In the documentation, >> >> ?http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_gluster_Command >> it says there is a "set-transport" command: >> ? ? Transport Commands >> ? ? ? ? volume set-transport VOLNAME TRANSPORT-TYPE [TRANSPORT-TYPE] ... >> ? ? ? ? ? ? Set the transport type for the specified volume. >> >> I wanted to try converting from RDMA to TCP, so this seemed like what I >> wanted. >> However, when I try it on my 3.1.1 installation, I get: >> ? ? # gluster volume set-transport RaidData tcp >> ? ? unrecognized word: set-transport (position 1) >> It does not seem to be listed by "gluster volume help", either. >> >> I'm not sure whether this is a documentation bug or a bug in the >> "gluster" command. >> >> >> .. Lana (lana.deere at gmail.com) >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >
