Problem using lvm as storage

[myk]

pve集群使用lvm作为共享存储。在某个节点上创建虚拟机后，在其他节点上无法通过lsblk查看新的虚拟机硬盘。可以通过lvscan查看，重启节点后就可以看到。有什么办法可以避免重新启动吗？
The pve cluster uses lvm as shared storage. After a virtual machine is created on a node, the new virtual machine hard disk cannot be viewed on other nodes through lsblk. It can be viewed through lvscan and can be seen after restarting the node. Is there any way to avoid restarting?

 

[jsterr]

pve集群使用lvm作为共享存储。在某个节点上创建虚拟机后，在其他节点上无法通过lsblk查看新的虚拟机硬盘。可以通过lvscan查看，重启节点后就可以看到。有什么办法可以避免重新启动吗？
The pve cluster uses lvm as shared storage. After a virtual machine is created on a node, the new virtual machine hard disk cannot be viewed on other nodes through lsblk. It can be viewed through lvscan and can be seen after restarting the node. Is there any way to avoid restarting?

lvm is not a shared storage, only when you use it on top of iscsi for example. see https://pve.proxmox.com/wiki/Storage

 

[bbgeek17]

When using LVM thick as a layer on top of shared storage, the LVM slices are selectively activated on the "primary" node for that VM. If I remember correctly, they are not then de-activated when the VM moves. So eventually you will see the slices on all nodes.
However, that does not mean that you can access them simultaneously across multiple nodes. Proxmox will be the arbiter of which node will be able to access the slice.
So what you are seeing is normal behaviour.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox