Bug 807126 - Rebalance status does not show the actual number of files migrated
Summary: Rebalance status does not show the actual number of files migrated
Alias: None
Product: GlusterFS
Classification: Community
Component: core   
(Show other bugs)
Version: pre-release
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: shishir gowda
QA Contact: shylesh
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
Reported: 2012-03-27 05:39 UTC by shylesh
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-24 17:39:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description shylesh 2012-03-27 05:39:17 UTC
Description of problem:
status showing number of files migrated has wrong information about the number

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

How reproducible:

Steps to Reproduce:
1. create a volume with single brick
2. create 20 files on the mount point
3. add another brick and initiate rebalance
4. check the status , when complete check the number of files rebalanced from the status and compare with the number of files present in the newly added brick
Actual results:
the number doesn't match with the actual number of files migrated.

Expected results:

Additional info:

Comment 1 Anand Avati 2012-04-25 11:05:43 UTC
CHANGE: http://review.gluster.com/3013 (rebalance: handshake_event_notify to make fsd talk to glusterd) merged in master by Vijay Bellur (vijay@gluster.com)

Comment 2 shylesh 2012-05-22 08:55:03 UTC
This issue is still seen on 3.3.0qa42, I migrated only one file using remove-brick but Rebalanced count says 0 files migrated.

Comment 3 shylesh 2012-05-22 09:17:38 UTC
For rebalance it's working fine hence moving this bug to verified state and opening a new bug for remove-brick

Note You need to log in before you can comment on or make changes to this bug.