public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs 2/2] pvesm: update features for LVM,iSCSI,FC,SAS
Date: Thu, 2 Jul 2026 13:46:00 +0200	[thread overview]
Message-ID: <cd7b71b3-16d7-4c79-98d6-299d7d7e839a@proxmox.com> (raw)
In-Reply-To: <s8ov7ax62s7.fsf@toolbox>



On  2026-07-02  13:37, Maximiliano Sandoval wrote:
> Aaron Lauterer <a.lauterer@proxmox.com> writes:
> 
>> 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
> 
> Technically, neither iSCSI storage plugin supports snapshots, what
> supports snapshots is a LVM storage on top of a iSCSI block device. I
> would personally keep the `no` and add a footnote saying that it is
> possible to have snapshots on a LVM storage with savc on top of the
> iSCSI storage.

Which is why I framed the footnotes to emphasize that multipathing + LVM 
is needed.
And realistically, that combination is the only way the vast majority of 
our users are using shared block storage.  I see it as a "full package" 
that needs to be configured before you can actually use the whole stack 
as shared storage. FC/SAS/iSCSI alone without LVM is rather useless, 
except for maybe very esoteric use cases.
We would rather not give the wrong impression that it is not possible 
for someone who very briefly takes a glimpse at the table.




  reply	other threads:[~2026-07-02 11:46 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 ` [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 [this message]
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=cd7b71b3-16d7-4c79-98d6-299d7d7e839a@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=m.sandoval@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal