Bug 1034643 - remove-brick status shows incorrect data for skipped files
Summary: remove-brick status shows incorrect data for skipped files
Keywords:
Status: CLOSED DUPLICATE of bug 1019846
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs
Version: 2.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-26 09:32 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-26 11:03:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 ***


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