Missing Features

[KingMotley]

Set drives in the DrivePool as being already duplicated.  Part of my DrivePool is a Raid-6 array (another part is RAID-1), so anything that gets put there wouldn't need to be duplicated to another disk. -- Possibly fixed if you could create Pool-in-Pool.

I'd like to be able to set individual max fill settings per drive.  Some drives I don't want completely filled, but others I do.

I'd like DrivePool to understand that one of my disks is actually a cache for a CloudDrive, and not attempt to move files off of it to the CloudDrive to make space (because it won't... The files will just sit in the CloudDrive write cache for a LONG time), which sends the balancing mechanism into an endless loop of trying to empty the drive... Essentially turning the entire disk into a CloudDrive write cache.

 

My current DrivePool:

14 3TB drives in a RAID-6.

2 10TB drives in a RAID-1 (CloudDrive cache here).

1 63TB CloudDrive.

 

Not in DrivePool:

1 6TB drive (mostly empty)

1 3TB drive (half empty)

2 256GB SSD drives in a RAID-0 (mostly full)

[Christopher (Drashna)]

Well, the "Drive Usage Limiter" can actually be used to facilitate this.  You can see the specific disk or disks to not store duplicate data ("original" or "copy"). 

 

That said, we are looking into duplication grouping and/or recursive pooling (pool in a pool). 

 

 

As for the balancing, it really depends on why this is occurring.  If I had to guess, I'd say that the disk in question is pretty full (like 90+% full).  If this is the case, then this may be normal.  ANd you can "fix" this by disabling the "Prevent Drive Overfill" balancer.