[Bugs] [Bug 1157381] mount fails for nfs protocol in rdma volumes
bugzilla at redhat.com
bugzilla at redhat.com
Wed Nov 19 09:44:59 UTC 2014
https://bugzilla.redhat.com/show_bug.cgi?id=1157381
--- Comment #16 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8975 committed in master by Niels de Vos
(ndevos at redhat.com)
------
commit f380e2029d608f97e3ba9a728605e1d798b09e8d
Author: Jiffin Tony Thottan <jthottan at redhat.com>
Date: Tue Oct 21 08:59:46 2014 -0400
rdma :mount fails for nfs protocol in rdma volumes
When we mount rdma only volume or tcp,rdma volume using newly
peer probed IP's(nfs-server on new nodes) through nfs protocol,
mount fails for rdma only volume and mount happens with
help of tcp protocol in the case of tcp,rdma volumes. That is for
newly added servers will always get transport type as "socket".
This is due to nfs_transport_type is exported correctly and
imported wrongly.
This can be verified by the following ,
* Create a rdma only volume or tcp,rdma volume
* Add a new server into the trusted pool.
* Checkout the client transport type specified nfs-server
volgraph.It will be always tcp(socket type) instead of rdma.
* And also for rdma only volume in the nfs log, we can see
'connection refused' message for every reconnect between
nfs server and glusterfsd.
BUG: 1157381
Change-Id: I6bd4979e31adfc72af92c1da06a332557b6289e2
Author: Jiffin Tony Thottan <jthottan at redhat.com>
Signed-off-by: Jiffin Tony Thottan <jthottan at redhat.com>
Reviewed-on: http://review.gluster.org/8975
Reviewed-by: Meghana M <mmadhusu at redhat.com>
Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-by: Niels de Vos <ndevos at redhat.com>
Tested-by: Niels de Vos <ndevos at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=JyGcHtgWnq&a=cc_unsubscribe
More information about the Bugs
mailing list