[Gluster-users] Missing "gluster volume set-transport" command
mrobbert at mines.edu
Thu Dec 9 09:00:54 PST 2010
I have been told that doing that is against best practice although I have yet to see where this best practice is documented. My recently missing files have been blamed on the fact that I deleted and re-created a volume on bricks with existing data. Due to the fact that RDMA seems to be having problems and apparently isn't even known to be working on the OFED that is shipped with any Linux distribution it would be good to have a supported way to switch between RDMA and TCP. Is there any reason that both can't be used?
On Dec 8, 2010, at 4:47 PM, Craig Carl 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.
> Craig Carl
> Senior Systems Engineer
> On 12/08/2010 08:01 AM, Lana Deere wrote:
>> In the documentation,
>> 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
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users