It looks like you're new here. If you want to get involved, click one of these buttons!
In order to better support our growing community we've set up a new more powerful forum.
The new forum is at: http://community.covecube.com
The new forum is running IP.Board and will be our primary forum from now on.
This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.
I've noticed some odd behavior with DrivePool's balancing, and I think the mechanism could use some refinement. While writing to the drive that has the most free space sounds like a good idea, this presents a problem when the pool consists of drives of varying sizes.
Imagine a pool consisting of two 3TB drives, two 2TB drives, and two 1TB drives. Currently, DrivePool won't write anything to the 2TB drives until the 3TB drives are at least one-third full, and will keep those 1TB drives empty until the 3TB are two-thirds full and the 2TB drives are half-full.
A more balanced approach would be to write to the drives that have the most percentage free space, rather than absolute free space, to more evenly spread the data (not to mention the I/O load and wear & tear) across all of the drives. I would rather have all of my drives 30% full than have all my data concentrated on just my largest drives.