Create & Configure Volumes
Select the type of the volume from the Volume Type section. The available volume types are File System (NFS and/or CIFS) and Block Device (iSCSI LUN).
Thin Provision and Thick Provision
Thin-provisioning allows a volume to acquire storage from its Storage Pool on an as-needed basis, as new data is written to the volume. Thin-provisioning enables many volumes to share a storage pool without an upper limit being placed on the volume itself (the only upper limit to the volume's size is available space in the pool).
Thick-provisioned volumes reduce the amount of space available in the Storage Pool by reserving this space for use by a specific volume. When a thick-provisioned volume reaches its maximum volume size, no more data can be written, and a volume full error will be returned for writes to a full volume. In addition, replication tasks will fail with an 'Out of Space' error if not enough space is provisioned. Thick-provisioned volumes can be re-sized at any time to add space (or return space to the storage by reducing the volume size).
Volume Size:
Once a Storage Pool has been selected for a thick-provisioned volume, the amount of available space to allocate is displayed below the Volume Size field, as shown in the example below.
The Volume Size value can be any valid numeric value; e.g., 10, 12.5, 100.0, 1.25
Storage Optimization
Select the required option for storage optimization in the Storage Optimization Options section. The available options are Compression and Deduplication. The Compression type saves disk space but requires more of CPU space. The Deduplication type eliminates duplicates but consumes more memory space.
When compressing a significant amount of data, be sure to observe the amount of actual CPU consumed during a typical day, and if necessary, add more CPU capacity to the SoftNAS® VM as required to ensure compression is fast and efficient. If data is not highly compressible, then disabling compression provides a better performance tradeoff.
It is recommended to avoid using deduplication unless the data is highly-duplicative, because of the memory impact of deduplication. It is estimated that for every terabyte of deduplicated data managed, two gigabytes of memory is required for the deduplication lookup tables. These tables compete with cache memory, which can reduce the overall performance of SoftNAS®.