Bug 1761486 - DHT- gluster rebalance status shows wrong data size after rebalance is completed successfully
Summary: DHT- gluster rebalance status shows wrong data size after rebalance is comple...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.5.z Batch Update 1
Assignee: Sanju
QA Contact: Sayalee
URL:
Whiteboard:
Depends On:
Blocks: 1762438
TreeView+ depends on / blocked
 
Reported: 2019-10-14 13:47 UTC by bipin
Modified: 2020-02-03 05:02 UTC (History)
12 users (show)

Fixed In Version: glusterfs-6.0-23
Doc Type: Bug Fix
Doc Text:
Previously, after rebalance was completed, if the glusterd was rebooted gluster volume rebalance status was displaying the wrong size. Now, rebalance status displays the size correctly.
Clone Of:
: 1762438 (view as bug list)
Environment:
Last Closed: 2020-01-30 06:42:48 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0288 0 None None None 2020-01-30 06:43:08 UTC

Description bipin 2019-10-14 13:47:50 UTC
Description of problem:
=======================
While doing a gluster re-balance from 1*(4+2) to 2*(4+2) and then to 3*(4+2),the re-balance status shows inconsistency (wrong data size) after the re-balance is completed. The re-balance status shows proper data till 4~6 hours of completion, then it mismatches. This was seen in both 2*(4+2) and 3*(4+2) configuration. Though the size was in GB, after the completion of re-balance it shows in PB.


Version-Release number of selected component (if applicable):
============================================================
glusterfs-6.0-15.el7rhgs.x86_64

How reproducible:
================
2/2

Steps:
=====
1.Create a RHHI-V setup with 3 node config
2.Create a disperse volume of 1*(4+2)
3.Start writing fio IO's using a gluster client and wait till its completed (say 400GB)
4.Now add brick and it's 2*(4+2) and start re-balance and wait till it completes
5.After 4-5 hours check the re-balance status, it shows incorrect data size
6.Repeat step 3 and 4 ,now it becomes 3*(4+2)
7.Start re-balance and wait till the re-balance is completed
8.Check the re-balance status as mentioned in step 5


Actual results:
==============
Showing wrong file size (in Peta Byte)


Expected results:
=================
Should show actual size


Additional info:
===============

Comment 24 Anjana KD 2020-01-29 17:28:20 UTC
have updated the doc text kindly verify the doc text- field.

Comment 26 errata-xmlrpc 2020-01-30 06:42:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0288


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