-|Description |PVE type |Level |Shared|Snapshots|Stable
-|ZFS (local) |zfspool |file |no |yes |yes
-|Directory |dir |file |no |no |yes
-|NFS |nfs |file |yes |no |yes
-|GlusterFS |glusterfs |file |yes |no |yes
-|LVM |lvm |block |no |no |yes
-|LVM-thin |lvmthin |block |no |yes |yes
-|iSCSI/kernel |iscsi |block |yes |no |yes
-|iSCSI/libiscsi |iscsidirect |block |yes |no |yes
-|Ceph/RBD |rbd |block |yes |yes |yes
-|Sheepdog |sheepdog |block |yes |yes |beta
-|DRBD9 |drbd |block |yes |yes |beta
-|ZFS over iSCSI |zfs |block |yes |yes |yes
-|=========================================================
-
-TIP: It is possible to use LVM on top of an iSCSI storage. That way
-you get a 'shared' LVM storage.
+|Description |Plugin type |Level |Shared|Snapshots|Stable
+|ZFS (local) |zfspool |both^1^|no |yes |yes
+|Directory |dir |file |no |no^2^ |yes
+|BTRFS |btrfs |file |no |yes |technology preview
+|NFS |nfs |file |yes |no^2^ |yes
+|CIFS |cifs |file |yes |no^2^ |yes
+|Proxmox Backup |pbs |both |yes |n/a |yes
+|GlusterFS |glusterfs |file |yes |no^2^ |yes
+|CephFS |cephfs |file |yes |yes |yes
+|LVM |lvm |block |no^3^ |no |yes
+|LVM-thin |lvmthin |block |no |yes |yes
+|iSCSI/kernel |iscsi |block |yes |no |yes
+|iSCSI/libiscsi |iscsidirect |block |yes |no |yes
+|Ceph/RBD |rbd |block |yes |yes |yes
+|ZFS over iSCSI |zfs |block |yes |yes |yes
+|===========================================================
+
+^1^: Disk images for VMs are stored in ZFS volume (zvol) datasets, which provide
+block device functionality.
+
+^2^: On file based storages, snapshots are possible with the 'qcow2' format.
+
+^3^: It is possible to use LVM on top of an iSCSI or FC-based storage.
+That way you get a `shared` LVM storage
+
+
+Thin Provisioning
+~~~~~~~~~~~~~~~~~
+
+A number of storages, and the QEMU image format `qcow2`, support 'thin
+provisioning'. With thin provisioning activated, only the blocks that
+the guest system actually use will be written to the storage.
+
+Say for instance you create a VM with a 32GB hard disk, and after
+installing the guest system OS, the root file system of the VM contains
+3 GB of data. In that case only 3GB are written to the storage, even
+if the guest VM sees a 32GB hard drive. In this way thin provisioning
+allows you to create disk images which are larger than the currently
+available storage blocks. You can create large disk images for your
+VMs, and when the need arises, add more disks to your storage without
+resizing the VMs' file systems.
+
+All storage types which have the ``Snapshots'' feature also support thin
+provisioning.
+
+CAUTION: If a storage runs full, all guests using volumes on that
+storage receive IO errors. This can cause file system inconsistencies
+and may corrupt your data. So it is advisable to avoid
+over-provisioning of your storage resources, or carefully observe
+free space to avoid such conditions.
+