Bug 1034643

Summary: remove-brick status shows incorrect data for skipped files
Product: Red Hat Gluster Storage Reporter: Vijaikumar Mallikarjuna <vmallika>
Component: glusterfsAssignee: Vijaikumar Mallikarjuna <vmallika>
Status: CLOSED DUPLICATE QA Contact: Sudhir D <sdharane>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.1CC: smohan, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-26 11:03:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Vijaikumar Mallikarjuna 2013-11-26 09:32:34 UTC
Description of problem:

remove-brick status show incorrect data for the 'skipped files'

Version-Release number of selected component (if applicable):
glusterfs 3.4rhs built on Nov 22 2013 15:48:48


How reproducible:
Always

Steps to Reproduce:
1. Create a distribute volume with three bricks
2. Create files and fill up the space of all the bricks:
   #cd /mnt; 
   #fallocate -l 1G file1
   #fallocate -l 1G file2
   #fallocate -l 1G file3
3. decommission of the brick by doing remove-brick start
4) check remove-brick status and rebalance status.
    rebalance status shows the correct result for skipped files, whereas remove-brick status shows '0' for skipped files. 


Actual results:
remove-brick status shows '0' for skipped files even though the rebalance process skipped some of the files


Expected results:
remove-brick status should show correct results for skipped files

Additional info:

Comment 2 Vijaikumar Mallikarjuna 2013-11-26 11:03:03 UTC
I just found that this issue is fixed as a part of bug# 1031887, so closing the bug as duplicate of bug# 1019846

*** This bug has been marked as a duplicate of bug 1019846 ***