postcd

I'm not sure what you mean here.
 
There is the read striping feature which may boost read speeds for you.
 
Aside from that, there is the file placement rules, which you could use to lock certain files or folders to the SSDs to get better read speeds.

I'm truly sorry, as it clearly can be done.
I won't delete the previous posts, but I will strike through everything that's incorrect so as to not to confuse anyone.
 
 
 

I've also made the move from Windows to Linux and wondered how to keep my pooled folders intact, having got used to seeing the content my folders in one pooled directory, it wasn't something I wanted to give up.
There is a neat solution. Using 'mhddfs' we can mount our multiple DP folders into one virtual directory, the folder structure remaining as it was under DP.
This isn't DP for Linux, all the work has been already done, all we are doing is pooling the PoolPart folders from each HDD and adding them to a new mount point, a virtual folder where they can be read and written to, complete with free space. I have 4 HDDs with PoolPart folders on them, but I see no reason why 'mhddfs' would have a limit.
There is more info here mhddfs guide, but instead of adding each partition just add the mount point of each PoolPart directory. (be sure to already have the HDDs mount at boot). So in my case I did this (my 4 HDDs already mounted at /media/dp1 etc)...
mint@mint-9:~$ sudo mkdir /mnt/drivepool mint@mint-9:~$ sudo mhddfs /media/dp1/PoolPart.760df304-1076-4a17-a53d-1a306e0b9808,/media/dp2/PoolPart.24256a59-5751-41c7-a2f7-c63e24c3c367,/media/dp3/PoolPart.bb5666e1-d315-4c07-9814-ac017e2287a2,/media/dp4/PoolPart.33b9f57d-862e-4d0d-a087-d4c9caeeefb8 /mnt/drivepool -o allow_other mhddfs: directory '/media/dp1/PoolPart.760df304-1076-4a17-a53d-1a306e0b9808' added to list mhddfs: directory '/media/dp2/PoolPart.24256a59-5751-41c7-a2f7-c63e24c3c367' added to list mhddfs: directory '/media/dp3/PoolPart.bb5666e1-d315-4c07-9814-ac017e2287a2' added to list mhddfs: directory '/media/dp4/PoolPart.33b9f57d-862e-4d0d-a087-d4c9caeeefb8' added to list mhddfs: mount to: /mnt/drivepool mhddfs: move size limit 4294967296 bytes  
Then we have the virtual mount point;  /mnt/ drivepool
 
mint@mint-9:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 7.8G 0 7.8G 0% /dev tmpfs 1.6G 2.2M 1.6G 1% /run /dev/sdg1 64G 14G 47G 23% / tmpfs 7.8G 942M 6.9G 12% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup /dev/sdb2 118G 85G 34G 72% /media/m4_win10 /dev/sdh2 69G 2.8G 63G 5% /media/data2 /dev/sda2 96M 32M 65M 33% /boot/efi /dev/sdc1 1.4T 997G 401G 72% /media/dp4 /dev/sde1 2.8T 2.3T 481G 83% /media/dp2 /dev/sdf1 3.7T 3.2T 478G 88% /media/dp1 /dev/sdd2 3.7T 3.2T 526G 86% /media/dp3 tmpfs 1.6G 52K 1.6G 1% /run/user/1000 /dev/sdh3 93G 16G 78G 17% /media/mint/38106A8210B140AD /dev/sdh1 56G 52G 3.6G 94% /media/mint/WIN10 /dev/sdg3 29G 18G 8.9G 67% /media/mint/data /media/dp1/PoolPart.760df304-1076-4a17-a53d-1a306e0b9808;/media/dp2/PoolPart.24256a59-5751-41c7-a2f7-c63e24c3c367;/media/dp3/PoolPart.bb5666e1-d315-4c07-9814-ac017e2287a2;/media/dp4/PoolPart.33b9f57d-862e-4d0d-a087-d4c9caeeefb8 12T 9.6T 1.9T 84% /mnt/drivepool I've kept the original PoolPart  folder names in case I go back to Windows and want to make DP work properly again, but if there is no need for that they can renamed to something shorter.
If everything works as you want it add the following line to fstab, (yours will be different)...
mhddfs#/media/dp1/PoolPart.760df304-1076-4a17-a53d-1a306e0b9808,/media/dp2/PoolPart.24256a59-5751-41c7-a2f7-c63e24c3c367,/media/dp3/PoolPart.bb5666e1-d315-4c07-9814-ac017e2287a2,/media/dp4/PoolPart.33b9f57d-862e-4d0d-a087-d4c9caeeefb8 /mnt/drivepool fuse defaults,allow_other 0 0 You may need to make permissions are set correctly, but assuming you've done all the prerequisites it fairly straightforward. 

We recommend BitLocker, actually. It's baked into windows, and works seamlessly with the system. Additionally, the "Automatical unlock" option works very well with the pool.
 
 
However, a lot of people do not trust BitLocker.
And TrueCrypt, it's forks and a few other encryption solutions bypass the VDS system altogether. Since that is a big part of DrivePool... they don't work. And would require a nearly complete rewrite of the code JUST to support these products. 
 
I'm not trying to start a debate, but just stating this and explaining why we don't support them.

I never updated this thread, but I encrypted my drives one by one, with no availability impact. I now have my entire pool encrypted at it works just as normal. Fantastic!