From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 1/2] pvesm: mention FC/SAS in the storage overview.
Date: Thu, 2 Jul 2026 13:08:55 +0200 [thread overview]
Message-ID: <20260702110856.2205894-1-a.lauterer@proxmox.com> (raw)
While not a dedicated storage plugin, it is possible to use FC and SAS
attached block storage.
Make it clear that it works and can be used with the snapshots as a
volume chain feature as it needs LVM on top.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvesm.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/pvesm.adoc b/pvesm.adoc
index 97feca0..b43ca42 100644
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -79,6 +79,7 @@ nodes that can be accessed as RBD (RADOS Block Device).
|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
|Ceph/RBD |rbd |block |yes |yes |yes
|ZFS over iSCSI |zfs |block |yes |yes |yes
|========================================================================
@@ -105,6 +106,12 @@ 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.
+
+
Thin Provisioning
~~~~~~~~~~~~~~~~~
--
2.47.3
next 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 Aaron Lauterer [this message]
2026-07-02 11:08 ` [PATCH docs 2/2] pvesm: update features for LVM,iSCSI,FC,SAS Aaron Lauterer
2026-07-02 11:37 ` 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-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox