+++ This bug was initially created as a clone of Bug #1173734 +++ Description of problem: When I try to mount an RDMA volume without an IB interface I get the following logs: +------------------------------------------------------------------------------+ [2014-12-08 22:18:56.669319] W [rdma.c:1082:gf_rdma_cm_event_handler] 0-testvol-client-3: cma event RDMA_CM_EVENT_ADDR_ERROR, error -19 (me: peer [2014-12-08 22:18:56.669361] E [MSGID: 108006] [afr-common.c:4293:afr_notify] 0-testvol-replicate-1: All subvolumes are down. Going offline until atleast one of them comes back up. [2014-12-08 22:18:56.672226] I [fuse-bridge.c:5042:fuse_graph_setup] 0-fuse: switched to graph 0 [2014-12-08 22:18:56.672473] I [fuse-bridge.c:3971:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.22 kernel 7.13 [2014-12-08 22:18:56.672745] W [fuse-bridge.c:757:fuse_attr_cbk] 0-glusterfs-fuse: 2: LOOKUP() / => -1 (Transport endpoint is not connected) [2014-12-08 22:18:56.684194] I [fuse-bridge.c:4883:fuse_thread_proc] 0-fuse: unmounting /gluster-mount [2014-12-08 22:18:56.684519] W [glusterfsd.c:1182:cleanup_and_exit] (--> 0-: received signum (15), shutting down [2014-12-08 22:18:56.684545] I [fuse-bridge.c:5561:fini] 0-fuse: Unmounting '/gluster-mount'. Is there any way we can make the error: cma event RDMA_CM_EVENT_ADDR_ERROR, error -19 More descriptive so the user knows that there is an issue finding / connecting with an RDMA device? Version-Release number of selected component (if applicable): glusterfs-3.6.0.38-1.el6.x86_64 How reproducible: Every time Steps to Reproduce: 1. Try to mount an RDMA volume without a properly configured IB device. 2. 3. Actual results: Mount fails as expected, but log message is cryptic. Expected results: A more clear log message. Additional info:
REVIEW: http://review.gluster.org/9756 (rdma:enhance logging when a connection error occur) posted (#1) for review on master by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/9756 committed in master by Vijay Bellur (vbellur) ------ commit 1a4e7362af1f351f389b73f9ae9c0b1fa423f7a3 Author: Mohammed Rafi KC <rkavunga> Date: Thu Feb 26 16:01:51 2015 +0530 rdma:enhance logging when a connection error occur Change-Id: I6146307949a3d852d3af5f8b273004ad6b27451b BUG: 1196584 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/9756 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Humble Devassy Chirammal <humble.devassy> Reviewed-by: Raghavendra Talur <rtalur> Reviewed-by: Vijay Bellur <vbellur>
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