Description of problem: When we create a volume with transport type as tcp,rdma, and fuse mount with rdma, it silently mounts as tcp. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Create a gluster volume with tcp,rdma transport 2. Start the volume 3.fuse mount with rdma transport Actual results: Mount shows successful, but mounts with transport type tcp. Snippet of Mount log volume test8-client-0 type protocol/client option send-gids true option password d62b2811-947d-4ea3-a76c-d80ab0d78fb1 option username 370718a0-7810-45d9-b0ca-df7c21aadb1a option transport-type socket option remote-subvolume /home/brick20 option remote-host 192.168.44.105 option ping-timeout 42 end-volume Expected results: Mounting should takes place as rdma transport, and mount log should contain volume test8-client-0 type protocol/client option send-gids true option password d62b2811-947d-4ea3-a76c-d80ab0d78fb1 option username 370718a0-7810-45d9-b0ca-df7c21aadb1a option transport-type rdma option remote-subvolume /home/brick20 option remote-host 192.168.44.105 option ping-timeout 42 end-volume Additional info:
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#1) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#2) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#3) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#4) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#5) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#6) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#7) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Fuse mount of a tcp,rdma volume with transport=rdma mounts as tcp) posted (#8) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Wrong volfile fetch on fuse mounting tcp,rdma volume via rdma) posted (#9) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Wrong volfile fetch on fuse mounting tcp,rdma volume via rdma) posted (#10) for review on master by Anoop C S (achiraya)
REVIEW: http://review.gluster.org/8498 (rdma: Wrong volfile fetch on fuse mounting tcp,rdma volume via rdma) posted (#11) for review on master by Anoop C S (achiraya)
COMMIT: http://review.gluster.org/8498 committed in master by Raghavendra G (rgowdapp) ------ commit c566e914a1ae84b18e20c917474be3028cd1b5de Author: Anoop C S <achiraya> Date: Wed Nov 12 18:02:15 2014 +0530 rdma: Wrong volfile fetch on fuse mounting tcp,rdma volume via rdma As of now for both tcp only volumes and rdma only volumes, volfile names are in the format <volname>-fuse.vol. This patch will change the client volfile namings as shown below. * TCP mounts always use <volname>-fuse.vol * RDMA mounts always use <volname>.rdma-fuse.vol Following the above naming convention, for tcp,rdma volumes both volfiles will be present under /var/lib/glusterd/vols/<volname>/ such that rdma only volume can be mounted as mount -t glusterfs -o transport=rdma <server/ip>:/<volname> <mount-point> OR mount -t glusterfs <server/ip>:/<volname>.rdma <mount-point> The above command format can also be used to fuse mount a tcp,rdma volume via rdma transport. When we try to fuse mount a tcp,rdma volume with transport-type as rdma it silently mounts via tcp. This change will also make sure that it fetches the correct volfile based on the transport-type specified from client side. BUG: 1131502 Change-Id: I34da4b01ac813b69494a43188f51145457412923 Signed-off-by: Anoop C S <achiraya> Reviewed-on: http://review.gluster.org/8498 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user