Space within a storage pool is shared between all shares. Filesystems can grow or shrink
dynamically as needed, though it is also possible to enforce space restrictions on a per-share
basis. Quotas and reservations can be enforced on a per-filesystem basis. Quotas can also be
enforced per-user and per-group. For more information on managing space usage for filesystems,
including quotas and reservations, see the Space Management section.
The logical size of the LUN as exported over iSCSI. This property is only valid for LUNs. This
property controls the size of the LUN. By default, LUNs reserve enough space to completely fill the
volume. See the Thin
provisioned property for more information. Changing the size of a LUN while actively
exported to clients may yield undefined results. It may require clients to reconnect and/or cause
data corruption on the filesystem on top of the LUN. Check best practices for your particular iSCSI
client before attempting this operation.
Controls whether space is reserved for the volume. This property is only valid for LUNs. By
default, a LUN reserves exactly enough space to completely fill the volume. This ensures that
clients will not get out-of-space errors at inopportune times. This property allows the volume size
to exceed the amount of available space. When set, the LUN will consume only the space that has been
written to the LUN. While this allows for thin provisioning of LUNs, most filesystems do not expect
to get "out of space" from underlying devices, and if the share runs out of space, it may cause
instability and/or data corruption on clients.
When not set, the volume size behaves like a reservation excluding snapshots. It therefore has
the same pathologies, including failure to take snapshots if the snapshot could theoretically
diverge to the point of exceeding the amount of available space. For more information, see Project - Reservation.