Hi,
pveversion below, 3 nodes cluster.
We need to stop an iSCSI SAN for maintenance. OpenMediaVault.
Before that :
- we moved all VM disk to another storage (OK),
- we uncheck "enable" in LVM storage window (OK) based on iSCSI.
- we uncheck "enable" in iSCSI storage window (OK).
Thinking it was the correct way to do, we stopped the SAN.
As soon as the (diabled) SAN becomes unreachable, proxmox io delay goes up to 55%, and all cluster is totally frozen!
VMs seems to be running normally.
pvecm status answers correctly
pvesm frozen.
Easy to reproduce.
Restart the (deactivated) SAN and proxmox cluster immediately comes back!
Any idea?
Isn't there a more clever way to activate a storage when (and only when) a first VM disk is created, and to deactivate after removing le last disk on this storage?
What are we doing wrong?
Is there a clean way to temporarily deactivate an unused SAN?
Is it at all possible without removing LVM and target storages?
Christophe.
--
root@px1-c:/var/log# pveversion -v
proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve)
pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-3-pve: 4.13.13-34
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-20
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-6
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.4-pve2~bpo9
pveversion below, 3 nodes cluster.
We need to stop an iSCSI SAN for maintenance. OpenMediaVault.
Before that :
- we moved all VM disk to another storage (OK),
- we uncheck "enable" in LVM storage window (OK) based on iSCSI.
- we uncheck "enable" in iSCSI storage window (OK).
Thinking it was the correct way to do, we stopped the SAN.
As soon as the (diabled) SAN becomes unreachable, proxmox io delay goes up to 55%, and all cluster is totally frozen!
VMs seems to be running normally.
pvecm status answers correctly
pvesm frozen.
Easy to reproduce.
Restart the (deactivated) SAN and proxmox cluster immediately comes back!
Any idea?
Isn't there a more clever way to activate a storage when (and only when) a first VM disk is created, and to deactivate after removing le last disk on this storage?
What are we doing wrong?
Is there a clean way to temporarily deactivate an unused SAN?
Is it at all possible without removing LVM and target storages?
Christophe.
--
root@px1-c:/var/log# pveversion -v
proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve)
pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-3-pve: 4.13.13-34
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-20
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-6
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.4-pve2~bpo9