Especially in large disks, it would be great when creating a volume, if the desired free physical space was defined instead of the actual encrypted container volume space. That way, one could simply enter 1(MB) and the created volume would consume the entire physical volume space minus 1 MB (which would be left as free space in the physical drive). As is now, setting volume size to i.e. 3.64TB on a 4TB drive would leave several MBs of wasted unencrypted space.
This could exist as an option in the Creation Wizard: a "define free physical space left" checkbox (which would change the meaning of the entered data in the "size" textbox).
π
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Especially in large disks, it would be great when creating a volume, if the desired free physical space was defined instead of the actual encrypted container volume space. That way, one could simply enter 1(MB) and the created volume would consume the entire physical volume space minus 1 MB (which would be left as free space in the physical drive). As is now, setting volume size to i.e. 3.64TB on a 4TB drive would leave several MBs of wasted unencrypted space.
This could exist as an option in the Creation Wizard: a "define free physical space left" checkbox (which would change the meaning of the entered data in the "size" textbox).
I agree, it is recommended to add features that take into account disk format, cluster.