Search results

Ok, you can ignore everything I said. @alexskysilk is correct in the direction you should be troubleshooting. You used a word combination that has very specific meaning in the PVE context "zfs over iscsi". However, you are just using straight iSCSI and trying to lay client side ZFS on top of...

Keep in mind that OP is using ZFS/iSCSI scheme. ZFS volumes on the storage sever, their iSCSI exporting, and PVE iSCSI are managed by the native storage plugin. In fact, if I remember correctly, iscsiadm is not used. This approach uses built-in QEMU iSCSI interface. The fact that there are two...

Thank you for clarifying. There are many ZFS experts in this forum, I am not one of them. That said, I suspect that the ZFS/iSCSI plugin is sufficiently different from the Local ZFS plugin, where the ZFS replication is primarily integrated and tested. My guess is that in the current state the...

Thank you for sharing, @Hank42. In your post #25, it stood out to me that you mentioned holding some packages while upgrading others. In general, this is not a good idea. The various components of the system are interconnected, and partial upgrades can easily lead to inconsistencies. Unless...

Can you clarify, did you build DIY type storage servers that are running some sort of Linux and organizes the storage with ZFS internally? This is not an appliance type SAN? And these two storage servers are independent of each other? Blockbridge : Ultra low latency all-NVME shared storage for...

You may have to live with the current deployment time until a technical solution is implemented to address this limitation. There may be something on the horizon, but I do not have visibility into the development priorities of Proxmox Server Solutions GmbH. One option is to purchase a support...

Hi @lxiosjao , No. I am not sure if the new tech-preview PVE9 LVM snapshot-as-volume-chain may optimize anything for you. If I recall correctly, it still require 100% space overhead reservation for snapshots/clones. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

@Hank42, have you installed helper scripts on your system at any point? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @Ghosthawk , welcome to the forum. Can you please specify what SAN type/model you are using? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @nbani, @floh8 is correct. You can present the FC storage to all nodes in the cluster, configure the Multipath, and then layer the LVM that PVE can operate on as Storage Pool. The reason the FC is not called out in those documents, is because the PVE can create storage pools for the other...

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

There may be a slight advantage of having multiple LUNs and Multiple Targets from a queue depth perspective. However, that generally applies to very high performance storage with fast clients. Without knowing anything about your performance profile, and based solely on the fact that you have a...

Hi @ajezierski , welcome to the forum. You need to create LVM using the Multipath DM device, not the underlying direct physical devices. So to answer your question - one VG per unique LUN. In your case 3 Volume groups (or you can combine your LUNs into a single VG). You may find this article...

We use simple bash script for our workflow. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

PVE does not use Vendor section of the CI. I believe the hostname is set via metadata file when built-in CI is used You can easily check this by mounting the ISO after VM has booted and examining the content of the files. local-hostname": "HOSTNAME" Blockbridge : Ultra low latency all-NVME...

Hi @alma21, There is no mechanism to do so. Theoretically, a window exists where both operations could be executed at the same time. In practice, however, the likelihood of this happening is very low. This is especially true in a business environment, where even routine operations such as...

Bieten Sie die Vorteile von Berliner vs. Pfannkuchen vs. Krapfen Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hallo @ce3rd, vielleicht interessiert dich auch die Diskussion in diesem Thread: https://forum.proxmox.com/threads/understanding-qcow2-risks-with-qemu-cache-none-in-proxmox.175933/#post-816074 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

@Impact is correct, one VM has local-lvm backing TPM disk, the other directory/raw. Raw file format does not support snapshot capability. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

@unsichtbarre , if you feel that your question was answered you can mark the thread as SOLVED by editing the first message and selecting the appropriate subject dropdown prefix. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox