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:
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.
RDMA on IB works in 3.5. Please upgrade to a current 3.5 release if you need RDMA.