Re: [pve-devel] iscsi and multipathing

["DERUMIER, Alexandre via pve-devel" <pve-devel@lists.proxmox.com>]

[-- Attachment #1: Type: message/rfc822, Size: 13112 bytes --]

From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] iscsi and multipathing
Date: Fri, 18 Apr 2025 06:24:28 +0000
Message-ID: <83233075ec35d1543ab7eb4cb19c01b96a20af8c.camel@groupe-cyllene.com>

> 

Hi,

> Also when changing lun size would have been grown on the storage
> side,
> it would be handy to have a button in pve web gui to "refresh" the
> disk in the vm. The new size should be reflected in the hardware
> details of the vm. And the qemu prozess should be informed of the new
> disk size so the vm would not have to be shutdown and restarted.

>>Based on experience, I doubt it would be that easy. Refreshing of the
>>LUN sizes involves the SAN, the client, multipath and QEMU. There's
>>always at least one place where it doesn't update even with
>>`rescan-scsi-bus.sh`, `multipath -r`, etc.
>>If you have a reliable way to make all sides agree on the new size,
>>please let us know.


From what I remember to try to do it 10year ago, another complexity is
to to refresh the volume size on all nodes for vm migration.
(or it need refresh at each vm start).

That's why zfs over iscsi is using qemu iscsi driver, it's really more
simple. (but no multipath :/ )



[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel