From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 docs] pvesm: mark ZFS level as both
Date: Tue, 11 Apr 2023 13:04:42 +0200 [thread overview]
Message-ID: <20230411110442.362000-1-a.lauterer@proxmox.com> (raw)
ZFS can do both, and we do use both, block and file level functionality.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
changes since v1: rephrased the footnote for ZFS
pvesm.adoc | 39 +++++++++++++++++++++------------------
1 file changed, 21 insertions(+), 18 deletions(-)
diff --git a/pvesm.adoc b/pvesm.adoc
index 6ade1a4..651999a 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, which provide
+block device functionality.
-^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
next reply other threads:[~2023-04-11 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 11:04 Aaron Lauterer [this message]
2023-06-06 16:02 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230411110442.362000-1-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal