[Bugs] [Bug 1306922] Self heal command gives error "Launching heal operation to perform index self heal on volume vol0 has been unsuccessful"
bugzilla at redhat.com
bugzilla at redhat.com
Wed Feb 17 09:53:55 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1306922
--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13435 committed in release-3.7 by Pranith
Kumar Karampuri (pkarampu at redhat.com)
------
commit 45301bcd97825206f7f19b25a4ad722e7dc13cc6
Author: Ravishankar N <ravishankar at redhat.com>
Date: Mon Jan 18 12:16:31 2016 +0000
cli/ afr: op_ret for index heal launch
Backport of http://review.gluster.org/#/c/13303/
Problem:
If index heal is launched when some of the bricks are down, glustershd of
that
node sends a -1 op_ret to glusterd which eventually propagates it to the
CLI.
Also, glusterd sometimes sends an err_str and sometimes not (depending on
the
failure happening in the brick-op phase or commit-op phase). So the message
that
gets displayed varies in each case:
"Launching heal operation to perform index self heal on volume testvol has
been
unsuccessful"
(OR)
"Commit failed on <host>. Please check log file for details."
Fix:
1. Modify afr_xl_op() to return -1 even if index healing of atleast one
brick
fails.
2. Ignore glusterd's error string in gf_cli_heal_volume_cbk and print a
more
meaningful message.
The patch also fixes a bug in glusterfs_handle_translator_op() where if we
encounter an error in notify of one xlator, we break out of the loop
instead of
sending the notify to other xlators.
Change-Id: I957f6c4b4d0a45453ffd5488e425cab5a3e0acca
BUG: 1306922
Signed-off-by: Ravishankar N <ravishankar at redhat.com>
Reviewed-on: http://review.gluster.org/13435
Smoke: Gluster Build System <jenkins at build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LQoqn2aGnv&a=cc_unsubscribe
More information about the Bugs
mailing list