From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 4F68E1FF135 for ; Thu, 02 Jul 2026 13:09:34 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 0DABC213D3; Thu, 02 Jul 2026 13:09:34 +0200 (CEST) From: Aaron Lauterer 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 Message-ID: <20260702110856.2205894-2-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260702110856.2205894-1-a.lauterer@proxmox.com> References: <20260702110856.2205894-1-a.lauterer@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1782990532502 X-SPAM-LEVEL: Spam detection results: 0 DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: BTJQZMYEZ3JFTYNSYJUKP2N77VDEIJTL X-Message-ID-Hash: BTJQZMYEZ3JFTYNSYJUKP2N77VDEIJTL X-MailFrom: a.lauterer@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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 --- 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