andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

protocol/client: print a message regarding brick status in case of failure

Browse Source 
that way, it would help admins to look at the corresponding brick directly.

All credit goes to Amar.

Change-Id: I959df59111864cc0574945d827f8fe5f2d919491
BUG: 839021
Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
Reviewed-on: http://review.gluster.org/4341
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
This commit is contained in:
Krutika Dhananjay 2012-12-20 13:22:28 +05:30 committed by Vijay Bellur
parent 000e65d7af
commit ab7ffc3907
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xlators/protocol/client/src/client-handshake.c
View File

@ -1691,7 +1691,9 @@ client_query_portmap_cbk (struct rpc_req *req, struct iovec *iov, int count, voi
ret = -1;
gf_log (this->name, ((!conf->portmap_err_logged) ?
GF_LOG_ERROR : GF_LOG_DEBUG),
"failed to get the port number for remote subvolume");
"failed to get the port number for remote subvolume. "
"Please run 'gluster volume status' on server to see "
"if brick process is running.");
conf->portmap_err_logged = 1;
goto out;
}