Disk replacement

[Mathis]

Hey,

I got one small bug/problem and maybe a cool feature idea.

 

The problem:

I removed a harddisk (button "Remove...") and placed a new drive. The new drive is still being recognized as the old vendors model. How can you reset this information?

 

The idea:

While safely removing the drive, all resources being available should be used to copy the data over to the new drive, to maximize the data throughput. Mostly the new drives are simply faster than the old drive, so when striped reading out the other disks, the new drive may be capable of writing in the same speed. Currently only one drive is being used for copying, so the throughput is limited by maybe an older and slower drive model. It should be optional, so the user can choose whether to use striped reading for duplication to the new drive or not.

[Christopher (Drashna)]

Where is showing the information from?

 

As for most info like this, restarting the service (via "services.msc") is a good way to forcibly refresh disk information.

As for the copy priority, we do have a couple of options for that, depending on what version of StableBit DrivePool you're using.
 

 

For version 1.X:

http://wiki.covecube.com/StableBit_DrivePool_Advanced_Settings

For version 2.X

http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings

 

Set FileBalance_BackgroundIO to "True" and it should help.

 

Alternatively, the UI has an option to boost the priority for certain tasks, on the fly. At least in Version 2.X