Difference between revisions of "Storage: ZFS"
m (Protected "Storage: ZFS" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
Revision as of 14:25, 4 July 2017
Storage pool type: zfspool
This backend allows you to access local ZFS pools (or ZFS file systems inside such pools).
The backend supports the common storage properties content, nodes, disable, and the following ZFS specific properties:
Select the ZFS pool/filesystem. All allocations are done within that pool.
Set ZFS blocksize parameter.
Use ZFS thin-provisioning. A sparse volume is a volume whose reservation is not equal to the volume size.
The mount point of the ZFS pool/filesystem. Changing this does not affect the mountpoint property of the dataset seen by zfs. Defaults to /<pool>.
zfspool: vmdata pool tank/vmdata content rootdir,images sparse
File naming conventions
The backend uses the following naming scheme for VM images:
vm-<VMID>-<NAME> // normal VM images base-<VMID>-<NAME> // template VM image (read-only) subvol-<VMID>-<NAME> // subvolumes (ZFS filesystem for containers)
This specifies the owner VM.
This can be an arbitrary name (ascii) without white space. The backend uses disk[N] as default, where [N] is replaced by an integer to make the name unique.
ZFS is probably the most advanced storage type regarding snapshot and cloning. The backend uses ZFS datasets for both VM images (format raw) and container data (format subvol). ZFS properties are inherited from the parent dataset, so you can simply set defaults on the parent dataset.
|Content types||Image formats||Shared||Snapshots||Clones|
It is recommended to create an extra ZFS file system to store your VM images:
# zfs create tank/vmdata
To enable compression on that newly allocated file system:
# zfs set compression=on tank/vmdata
You can get a list of available ZFS filesystems with:
# pvesm zfsscan