Search results

Hi @tka222 , Given that your storage is FC based, the migration (presuming you mean live migration of VM between PVE hosts) does not carry a lot of data. Your best option is to create an LACP bond that provides a) redundancy for all traffic, most importantly cluster b) allows for some bandwidth...

Hi @RodolfoRibeiro , welcome to the forum! This topic is a common discussion point here on the forum. It is generally raised at least once a week, sometimes more. To address your questions: - Yes, many people run with this type of infrastructure in production - Yes, you can and should use...

In the PVE API here: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/disks/lvmthin and here: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/disks/wipedisk You can make a call to "Also wipe disks so they can be repurposed afterwards." I'd have to look to see how it is...

Removing an LVM slice (if VRTX-SSD is LVM based storage) is not enough to erase the data on the underlying disk. This has been discussed in the forum a few times, although I cant give you a link at this moment. You can check by running "lsblk" and 'blkid' on the hypervisor against the LVM slice...

If the pool ends at 249, then 240 is within the range. Pick an IP that is higher than 249 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thank you for the update @unsichtbarre . You can mark the thread as Solved, to keep the forum tidy, by editing the first message and selecting an appropriate subject prefix. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The file/location is not checked at the time of setting the option. It is possible that the config does not exist at the time of VM creation. One could dynamically generate the config on VM start. You will be notified at the time of VM start or migration if the CI config is missing...

You are the only person with full view and access to the system. You shared summary of what you think the system is and only partial snippets with us. There are a few possible theories, you can eliminate most of them by rebooting your host and observing what the system was able to re-establish...

Hi @unsichtbarre , The only explanation , based on the technical details you posted, is that you do indeed have a route between the two networks. You should be able to figure it out with "ping" command, traceroute, and by checking ARP tables. Blockbridge : Ultra low latency all-NVME shared...

Hi @alexx, there was a similar discussion recently here: https://forum.proxmox.com/threads/proxmox-with-48-nodes.174684 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

LVM is a PVE integrated way to use FC as shared storage. You can read this article to get high level understanding of the components involved: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/ Although it references iSCSI as underlying storage - the concepts are the same. You can...

Thank you for the update @RobFantini! Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @ProlyX , can you clarify "that" in your question? ZFS is not multi-initiator/multi-writer compatible. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @unsichtbarre , My guess is that the majority of people will never need this package, so there is no reason to create dependencies, or install it by default. Otherwise, it will be part of initramfs management on all installs. Blockbridge : Ultra low latency all-NVME shared storage for...

The snapshot support sits above the FC/Multipath layers. It requires LVM to be placed on top of the Multipath device, as well as, snapshot-as-volume-chain 1 attributed on the storage pool. This attribute is present on the referenced page, however the primary goal of the article does not focus on...

Thank you for the update @Elleni . There could be many possibilities, for example: https://forum.proxmox.com/threads/vms-loosing-network.180650/#post-838011 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thank you for the update @naps1saps . You can mark the thread as SOLVED by editing the first post and updating the subject prefix. Best of luck in your endeavors. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @Elleni, The first step is to go through standard Linux network troubleshooting. Capture the network state when everything is functioning correctly, then capture it again when the network is "broken". Compare the two states. Access the server via IPMI/BMC and perform basic checks: Is the...

It will skip the mounted paths and it will not show the space occupied by the directory in pre-mounted state. One can make some inference regarding the space usage but the safest method is to unmount the external device and check again. Blockbridge : Ultra low latency all-NVME shared storage...

What version of PVE are you running on each node? In PVE9 most of the database has moved to /var/lib/iscsi How are you managing iSCSI sessions? Are you using PVE storage pool or manual configuration? If former, is your cluster healthy? If later, are you sure that you set proper restart options...