From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 2/2] pvesm: update features for LVM,iSCSI,FC,SAS
Date: Thu, 2 Jul 2026 13:08:56 +0200 [thread overview]
Message-ID: <20260702110856.2205894-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20260702110856.2205894-1-a.lauterer@proxmox.com>
And reword the footnotes to mention the multipath guide that show to set
it up with LVM on top in detail.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvesm.adoc | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/pvesm.adoc b/pvesm.adoc
index b43ca42..5bd24b2 100644
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -77,9 +77,9 @@ nodes that can be accessed as RBD (RADOS Block Device).
|CephFS |cephfs |file |yes |yes |yes
|LVM |lvm |block |no^3^ |yes^4^ |yes
|LVM-thin |lvmthin |block |no |yes |yes
-|iSCSI/kernel |iscsi |block |yes |no |yes
-|iSCSI/libiscsi |iscsidirect |block |yes |no |yes
-|FC/SAS |native^6^ |block |yes |yes^4^ |yes
+|iSCSI/kernel |iscsi |block |yes^3^|yes^4^ |yes
+|iSCSI/libiscsi |iscsidirect |block |yes^3^|yes^4^ |yes
+|FC/SAS |native^6^ |block |yes^3^|yes^4^ |yes
|Ceph/RBD |rbd |block |yes |yes |yes
|ZFS over iSCSI |zfs |block |yes |yes |yes
|========================================================================
@@ -96,8 +96,11 @@ TiB sized), these operations may take several minutes, or in extreme cases, even
hours. If your setup is affected, create and remove snapshots while the VM is
shut down, expecting a long task duration.
-^3^: It is possible to use LVM on top of an iSCSI or FC-based storage.
-That way you get a `shared` LVM storage
+^3^: With iSCSI, FibreChannel (FC), or SAS block storage as shared storage in a
+cluster, LVM is used to split the LUN into virtual disks. The
+https://pve.proxmox.com/wiki/Multipath[Multipath Guide] explains how to
+configure it in a cluster, including multipathing which is usually a
+requirement in these scenarios.
^4^: Since {pve} 9, snapshots as a volume chain have been available for VMs.
These snapshots use separate volumes for the snapshot data and layer them. For
@@ -107,9 +110,7 @@ xref:pvesm_lvm_config[LVM configuration] section.
^5^ Technology preview with best-effort support.
^6^ Fibre Channel (FC) and SAS block storage is handled directly by the host
-without a dedicated storage plugin. The
-https://pve.proxmox.com/wiki/Multipath[Multipath Guide] explains how to set it
-up in a cluster.
+without a dedicated storage plugin.
Thin Provisioning
--
2.47.3
next prev parent reply other threads:[~2026-07-02 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 11:08 [PATCH docs 1/2] pvesm: mention FC/SAS in the storage overview Aaron Lauterer
2026-07-02 11:08 ` Aaron Lauterer [this message]
2026-07-02 11:37 ` [PATCH docs 2/2] pvesm: update features for LVM,iSCSI,FC,SAS Maximiliano Sandoval
2026-07-02 11:46 ` Aaron Lauterer
2026-07-02 13:55 ` applied: [PATCH docs 1/2] pvesm: mention FC/SAS in the storage overview 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=20260702110856.2205894-2-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.