From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E70758CD2 for ; Tue, 7 Mar 2023 11:40:13 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C873CACF7 for ; Tue, 7 Mar 2023 11:40:13 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 7 Mar 2023 11:40:13 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id CB59541DE3 for ; Tue, 7 Mar 2023 11:40:12 +0100 (CET) From: Aaron Lauterer To: pve-devel@lists.proxmox.com Date: Tue, 7 Mar 2023 11:40:11 +0100 Message-Id: <20230307104011.1013327-1-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.444 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_ASCII_DIVIDERS 0.8 Email that uses ascii formatting dividers and possible spam tricks KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs] pvesm: mark ZFS level as both X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Mar 2023 10:40:13 -0000 ZFS can do both, and we do use both, block and file level functionality. Signed-off-by: Aaron Lauterer --- A change to the column width was unfortunately needed. I renumbered the footnotes so that the first footnote starts with 1. We probably should also check again, if we cannot get dir storage functionility integrated in the ZFS storage module to also support ISOs, backups, etc etc. pvesm.adoc | 39 +++++++++++++++++++++------------------ 1 file changed, 21 insertions(+), 18 deletions(-) diff --git a/pvesm.adoc b/pvesm.adoc index 6ade1a4..08ad79c 100644 --- a/pvesm.adoc +++ b/pvesm.adoc @@ -67,27 +67,30 @@ data to different nodes. .Available storage types [width="100%",cols="<2d,1*m,4*d",options="header"] |=========================================================== -|Description |PVE type |Level |Shared|Snapshots|Stable -|ZFS (local) |zfspool |file |no |yes |yes -|Directory |dir |file |no |no^1^ |yes -|BTRFS |btrfs |file |no |yes |technology preview -|NFS |nfs |file |yes |no^1^ |yes -|CIFS |cifs |file |yes |no^1^ |yes -|Proxmox Backup |pbs |both |yes |n/a |yes -|GlusterFS |glusterfs |file |yes |no^1^ |yes -|CephFS |cephfs |file |yes |yes |yes -|LVM |lvm |block |no^2^ |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 +|Description |PVE 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^: On file based storages, snapshots are possible with the 'qcow2' format. +^1^: Disk images for VMs are stored in ZFS volume (zvol) datasets that provide +block storage. -^2^: It is possible to use LVM on top of an iSCSI or FC-based storage. -That way you get a `shared` LVM storage. +^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 -- 2.30.2