Why was here a rebalance task after I finished the storage firmware upgrade?

Boreas · Created Sep 10, 2019 14:21:41

Hi Jarvis, as I known, it's a normal phenomenon after system completed upgrade.it automatically triggerred by system, the purpose was to check whether the data has already evenly distributed to different disk.

this task is to evenly rebalance data on each disk, meanwhile evenly allocate the I/O read/write stress to each disk, to prevent one disk appear the high stress, to avoid the performance of whole disk domain slumping when one disk takes on too much stress.

Boreas · Created Sep 10, 2019 14:21:41

Hi Jarvis, as I known, it's a normal phenomenon after system completed upgrade.it automatically triggerred by system, the purpose was to check whether the data has already evenly distributed to different disk.

this task is to evenly rebalance data on each disk, meanwhile evenly allocate the I/O read/write stress to each disk, to prevent one disk appear the high stress, to avoid the performance of whole disk domain slumping when one disk takes on too much stress.

Boreas · Created Sep 10, 2019 14:26:03

Supplement, in general, when controller reboot or disk domain finish the disk expansion activity, it will trigger the disk domain starts the rebalance task.

It's a normal phenomenon.

Why was here a rebalance task after I finished the storage firmware upgrade?

Best answer

Third Party’s Trade Secret

My Followers

Enterprise

Consumer

Corporate

Carriers

Why was here a rebalance task after I finished the storage firmware upgrade?

Best answer

Third Party’s Trade Secret

My Followers