Description of problem: Execution of "gluster volume heal <volumename> [{full | info {healed | heal-failed | split-brain}}]" command should output meaningful messages Version-Release number of selected component (if applicable): mainline output of the execution of commands:- ---------------------------------------------- [root@APP-SERVER1 glusterfs]# gluster volume heal datastore Starting heal on volume datastore has been successful [root@APP-SERVER1 glusterfs]# gluster volume heal datastore full Starting heal on volume datastore has been successful [root@APP-SERVER1 glusterfs]# gluster volume heal datastore info Starting heal on volume datastore has been successful [root@APP-SERVER1 glusterfs]# gluster volume heal datastore info healed Starting heal on volume datastore has been successful [root@APP-SERVER1 glusterfs]# gluster volume heal datastore info heal-failed Starting heal on volume datastore has been successful [root@APP-SERVER1 glusterfs]# gluster volume heal datastore info split-brain Starting heal on volume datastore has been successful
CHANGE: http://review.gluster.com/3276 (Self-heald: Dump the event history completely) merged in master by Vijay Bellur (vijay)
CHANGE: http://review.gluster.com/3277 (Self-heald: Print the time stamp of the event-history) merged in master by Vijay Bellur (vijay)
CHANGE: http://review.gluster.com/3352 (Self-heald: Print the time stamp of the event-history) merged in release-3.3 by Vijay Bellur (vijay)
Bug is fixed. Verified on 3.3.0qa42