Red Hat Bugzilla – Bug 1154617
Fuse mounting of a tcp,rdma volume with rdma as transport type always mounts as tcp without any fail
Last modified: 2015-05-13 13:42:11 EDT
+++ This bug was initially created as a clone of Bug #1131502 +++ 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: --- Additional comment from Anand Avati on 2014-08-19 10:12:00 EDT --- 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@redhat.com) --- Additional comment from Anand Avati on 2014-09-08 08:29:12 EDT --- 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@redhat.com) --- Additional comment from Anand Avati on 2014-09-09 08:46:51 EDT --- 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@redhat.com) --- Additional comment from Anand Avati on 2014-09-13 11:27:38 EDT --- 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@redhat.com) --- Additional comment from Anand Avati on 2014-09-15 02:57:51 EDT --- 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@redhat.com) --- Additional comment from Anand Avati on 2014-09-26 04:08:58 EDT --- 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@redhat.com) --- Additional comment from Anand Avati on 2014-09-26 04:12:14 EDT --- 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@redhat.com) --- Additional comment from Anand Avati on 2014-10-13 01:51:52 EDT --- 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@redhat.com)
Verified on glusterfs-3.6.0.41.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0038.html