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: ===============
have updated the doc text kindly verify the doc text- field.
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