+++ This bug was initially created as a clone of Bug #955967 +++ Description of problem: DHT - rebalance - output of 'gluster volume rebalance <volname> start/start force/fix-layout start ' is ambiguous and poorly formatted Version-Release number of selected component (if applicable): 3.4.0.1rhs-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. Create a Distributed volume having 2 or more sub-volume and start the volume. 2. Fuse Mount the volume from the client-1 using “mount -t glusterfs server:/<volume> <client-1_mount_point>” mount -t glusterfs XXX:/<volname> /mnt/XXX 3. From mount point create some files and perform rename operation. or add brick to that volume or change sub-vol per dir option 4.Run rebalance command for that volume. [root@cutlass v1]# gluster volume rebalance v1 start volume rebalance: v1: success: Starting rebalance on volume v1 has been successful. ID: 7d9e997c-0f1d-453a-aaca-50137774fbe7 [root@cutlass v1]# gluster volume rebalance v1 fix-layout start volume rebalance: v1: success: Starting rebalance on volume v1 has been successful. ID: 6fc6e50a-1791-4e47-b784-fe3ca1e248fa [root@cutlass v1]# gluster volume rebalance v1 start force volume rebalance: v1: success: Starting rebalance on volume v1 has been successful. ID: 04d2f245-b701-4714-a37d-ee6d377f0ae9 Actual results: [root@cutlass v1]# gluster volume rebalance v1 start volume rebalance: v1: success: Starting rebalance on volume v1 has been successful. Expected results: ambiguous:- 'volume rebalance: v1: success:' - Does this mean rebalance on volume is completed and successful ? but remaining part says Starting rebalance on volume <vol_name> has been successful poorly formatted: the same information is displayed twice with poor formating 1.volume rebalance: v1: success: 2. Starting rebalance on volume v1 has been successful. Additional info: --- Additional comment from Scott Haines on 2013-09-27 13:07:46 EDT --- Targeting for 3.0.0 (Denali) release. --- Additional comment from Gaurav Kumar Garg on 2014-04-10 06:25:01 EDT --- @ Rachana Could you elaborate above problem. output of "#gluster volume rebalance v1 start" is "volume rebalance: v1: success: Starting rebalance on volume v1 has been successful." this means that starting of rebalancing on volume has been started but not finished. could you explain this problem.
REVIEW: http://review.gluster.org/7473 (glusterfs:ambiguous message remove when use rebalance <volname> start) posted (#3) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli:ambiguous message error out when use rebalance <volname> start) posted (#5) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli:ambiguous message remove when use rebalance <volname> start) posted (#7) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli:ambiguous message error out when use rebalance <volname> start) posted (#9) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli:ambiguous message error out when use rebalance <volname> start) posted (#10) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli:ambiguous message error out when use rebalance <volname> start) posted (#11) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#12) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#13) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#14) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#15) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#16) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#17) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#18) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/7473 (cli: Fixing ambiguous message error for rebalance <volname> start command) posted (#19) for review on master by Gaurav Kumar Garg (ggarg)
COMMIT: http://review.gluster.org/7473 committed in master by Vijay Bellur (vbellur) ------ commit c2a0e3f722583731599785d16f12be5b3472934b Author: ggarg <ggarg> Date: Mon Apr 14 16:38:15 2014 +0530 cli: Fixing ambiguous message error for rebalance <volname> start command Previously output message of command 'gluster volume rebalance <volname> start/start force/fix-layout start' was ambiguous and poorly formatted. Previously output message was: "volume rebalance: <volname>: success: Starting rebalance on volume <volname> has been successful." Now with this fix properly formatted output message is: "volume rebalance: <volname>: success: Rebalance on <volname> has been started Successfully. Use rebalance status command to check status of the rebalance process." Change-Id: I23268fc13b05d1b39ffe4c702d0e4f73085acd1c BUG: 1087487 Signed-off-by: ggarg <ggarg> Reviewed-on: http://review.gluster.org/7473 Tested-by: Gluster Build System <jenkins.com> 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