Bug 982757

Summary:	RMDA Volumes Silently Revert to TCP
Product:	[Community] GlusterFS	Reporter:	Ryan <ryade>
Component:	rdma	Assignee:	GlusterFS Bugs list <gluster-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.0-beta	CC:	bugs, gluster-bugs, kkeithle, matthew.a.nicholson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-14 13:14:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ryan 2013-07-09 19:34:42 UTC

Description of problem: RDMA Silently Reverts to TCP if there is a client issue/nonfunctioning RDMA subsystem


Version-Release number of selected component (if applicable): 3.4.beta4


How reproducible: Reliably


Steps to Reproduce:
1. Create an RDMA/TCP Volume
2. Unload the Kernel Module RDMA_CM on the client (if loaded)
3. Mount the volume via RDMA on the client

Actual results:

The volume will mount, report as RDMA mount, however TCP will be used as the transport mechanism.


Expected results:

The volume mount should either fail outright (since RDMA was explicitly defined) or revert to TCP with a warning message. 


Additional info:

Comment 1 Matt Nicholson 2013-07-10 19:08:16 UTC

Seeing this in out test 3.4beat4 setup, volumes with transport=tcp,rdma, when mounted explicitly with Rmda silently fail to tcp. A warning message @ mount time would be nice, or perhaps a mount option to prevent failover to tcp when specified.

Comment 2 Kaleb KEITHLEY 2014-10-14 13:14:40 UTC

RDMA on IB works in 3.5. Please upgrade to a current 3.5 release if you need RDMA.