Description of problem: carry on to this http://review.gluster.org/#/c/11469/ capture the error(s) - in most cases it will be 1 or 2 lines (not status exit codes but the true errors exposed in the log) [2016-04-28 14:21:29.109697] E [socket.c:2332:socket_connect_finish] 0-glusterfs: connection to 192.168.123.222:24007 failed (Connection timed out) [2016-04-28 14:21:29.109767] E [glusterfsd-mgmt.c:1819:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: 192.168.123.222 (Transport endpoint is not connected) when mount.glusterfs is called and an issue happens we have to read the errors out of the log, would like the true root cause error to simply be returned to the caller so the extra step of reading the log does not need to be performed. below is result of conversation with @prasanna kalever: I am just thinking what all you need to do is [1] # mount -t glusterfs --verbose -o log-level=ERROR $IP:/<Vol> /mnt/mountpoint Which will print the GF_LOG_ERROR messages, but I found that currently there is a bug w.r.t mount log-level, some where log_level from command args gets overwritten by log_level INFO, at-least in the master branch (which I will try to fix). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
@prasanna.kalever - is there any status on this? I think this was related to an existing BZ but can't find which one
Migrated to github: https://github.com/gluster/glusterfs/issues/574 Please follow the github issue for further updates on this bug.