+++ This bug was initially created as a clone of Bug #1547662 +++ Description of problem: After a replace brick, self-heal takes some time to start reconstructing the files, and when it starts, sometimes it pauses for a while. Version-Release number of selected component (if applicable): mainline How reproducible: always Steps to Reproduce: 1. create a disperse volume 2. replace one brick 3. check new brick contents Actual results: New brick is not being filled immediately. It can take some time to start moving files, and it might make pauses. Expected results: Self-heal should trigger immediately after replacing the brick and don't stop until finished healing all files. Additional info:
have tested this on 3.12.2-9 and I see selfheal kicks off immediately (as against when tested in 3.8.4-54.9 3.3.1 async, where it take a bit of a delay) hence moving to verified
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/RHSA-2018:2607