Bug 1065625 - Rebalance stop on distributed-stripe volume without add-brick
Summary: Rebalance stop on distributed-stripe volume without add-brick
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-15 08:22 UTC by Jiffin Tony Thottan
Modified: 2015-10-22 15:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Jiffin Tony Thottan 2014-02-15 08:22:45 UTC 
Description of problem:
Rebalance stop on a distributed-stripe volume without add-brick


Version-Release number of selected component (if applicable):
3.5.beta3


How reproducible:


Steps to Reproduce:
1.create a 2x2 dist-stripe volume
2.Start the volume
3.Run “ gluster volume rebalance $vol Stop ”

Actual results:
volume rebalance: dis-str2: success: rebalance process may be in the middle of a file migration.
The process will be fully stopped once the migration of the file is complete.
Please check rebalance process for completion before doing any further brick related tasks on the volume.

Expected results:
“Rebalance is not running on the volume $vol”

Additional info:
Fails also for dist-replicate volume
Comment 2 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC 
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.
Note You need to log in before you can comment on or make changes to this bug.