StableBit DrivePool for Windows Home Server 2011 Beta 1.0.2.6229 released

There has been another beta build from CoveCube! StableBit DrivePool development marches on – now its version 1.0.2.6229.

Here is how CoveCube describes this application:

• Combine all your hard drives into one big storage pool (except the system drive with the OS).
• Add and remove drives from the pool at any time without re-partitioning or manually moving folders.
• Create duplicated folders on the storage drive pool that are protected against single drive failure. If a drive fails on which a duplicated file was stored, the contents of that file will remain readable even without the drive.
• All your data is stored in standard NTFS files. You can always access your files even if the Windows Home Server completely crashes or this add-in can’t be used.

This beta version’s change log

1.0.2.6229

* Fixed settings / state getting reset on upgrading.
* Added UI option for network I/O prioritization to the Disks DrivePool tab.
After some testing, this option seems to be effective at minimizing stutter when streaming high bandwidth media
directly from the server (such as BluRay).
* Moved read striping option to the Disks DrivePool tab.
* [D] Added a new read striping algorithm called “block mode” after conducting some testing with read striping.
CoveFS will select the correct algorithm to use in real-time.
Added a number of read striping options to .config:
CoveFs_ReadStripingBlockMode
CoveFs_ReadStripingStripeSize
CoveFs_ReadStripingBlockModeNoCache
* [D] Added performance measuring instrumentation into the driver.
* Exposed CoveFS performance measurements, in real time, into the Dashboard.
Hidden feature exposed by hitting ‘P’ on the DrivePool tab.
* Added read striping and network I/O boost real-time visualizations to the DrivePool Disks tab.
When these features are actively working, you will see how much pool I/O is being affected, in percentages.
* Fixed installer service not starting on fresh install.
* Fixed delayed action firing too often, affecting much of the application. Delayed actions are used in the service
and Dashboard, not in the file system.: