forced drivepool measuring and checking

[Shooter3k]

Hello, I'm running 3 different pools currently, 30 disks with a total about 350tb. However, I'm currently running into some stability issues, which require me to push the reset button. When I do this, all 3 drivepools force themselves back into a "measuring" and then "checking" status, which takes about 24-36 hours to run for all 3 pools. 

Is there any way to stop this full 'measuring' and 'checking' every time this happens? If my machine has to reset once every few days, it's basically always trying to do a measuring and checking. 

If there is no way to stop this, is there any way to make it go as fast as physically possible? Perhaps having it use 100% of the disk speed and 100% cpu?

[Shane]

The only way I know of to stop an active remeasure is to stop the StableBit DrivePool service; any pools will continue to function but balancing won't occur until the service is started again.

You can set DrivePool to remeasure somewhat quicker by clicking the little ">>" icon to the right of the organizational bar in the GUI. You can also adjust the settings.json file (CoveFs_MeasureBackgroundTaskPriority and DrivePool_BackgroundTasksPriority - be sure to read this link first) if you wish to change the priority further.

There is an option in settings.json that is only described in the changelog - "Added PoolPartUpdates_AlwaysConsistent config option to disable the remeasure and duplication check passes after a missing disk comes back online" - but I do not know if it would apply to remeasuring after a forced reset.

[Shooter3k]

8 hours ago, Shane said:

The only way I know of to stop an active remeasure is to stop the StableBit DrivePool service; any pools will continue to function but balancing won't occur until the service is started again.

You can set DrivePool to remeasure somewhat quicker by clicking the little ">>" icon to the right of the organizational bar in the GUI. You can also adjust the settings.json file (CoveFs_MeasureBackgroundTaskPriority and DrivePool_BackgroundTasksPriority - be sure to read this link first) if you wish to change the priority further.

There is an option in settings.json that is only described in the changelog - "Added PoolPartUpdates_AlwaysConsistent config option to disable the remeasure and duplication check passes after a missing disk comes back online" - but I do not know if it would apply to remeasuring after a forced reset.

Thank you for the information.

If you push the reset button on your machine right now, will it go through the whole process of measuring and checking? 

[Christopher (Drashna)]

A forced reboot should a remeasure pass, yeah.