Description of problem: ====================== when verifying bz#1526373 - Brick Multiplexing: Gluster volume start force complains with command "Error : Request timed out" when there are multiple volumes heal info shows the brick as transport end point error, ie still not online. even when the brick is online. this obviously leads to more entries pending heals as more IOs are pumped in the chance of hitting this problem is about 50% Version-Release number of selected component (if applicable): =========== glusterfs-server-3.8.4-52.3.el7rhgs.x86_64 How reproducible: ================= 2/4 Steps to Reproduce: 1. create a brick mux setup 2. create about 60 ecvols all 1x(4+2) 3. start the volumes 4. pump IOs to the base volume and another volume(i created an extra ecvol for this) 5.now kill a brick say b1 6. use volume force start of any volume(some vol in higher ascending order say vol15 or vol20 ...and not the base volume) 7. now start other volumes ie the mounted vols using vol force Actual results: ========= healinfo still sees brick down shd fails to start on one of the vols (raised a seperate BZ#1530217 - Brick multiplexing: glustershd fails to start on a volume force start after a brick is down) logs of BZ#1530217 can be used
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-2018:0083