That's awesome to hear! Glad we could help!
@fabian pinging you here, It may be worth for PVE team to look at including this fix sooner than later!
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
@Johannes S: I could be mistaken, but it appears to me that you and @iceph03nix are talking about the same thing : Veeam's agents.
@iceph03nix :
A dedicated backup/recovery company has years of head start here. It's in Veeam's DNA. Proper...
I want to reference below info/link ... I assume that the Starwind PVE thin plugin is also affected ... at least you should be aware ....
Why LVM-Thin Cannot Be Shared Storage in Proxmox...
Hi @jorge barriga ,
You should look into OCFS. There are a few 3rd party guides floating around, including on this forum.
There is no official supported way to do what you want with PVE framework.
Blockbridge : Ultra low latency all-NVME shared...
No, just this VM. isolcpus already keeps everything else off those cores, other VMs included, so nothing to change there.
I meant the affinity: line on this VM. Since you're pinning the vcpu threads by hand anyway, think of affinity: as where...
Hi @alma21
Only Veeam can give you this level of technical details.
From our testing of their initial plugin release - they bypass the PVE completely and interact with QEMU directly.
the filter is used with and without fleecing. Fleecing...
Hi @molotch ,
If what you are showing for the sources.list is the entirety of the file, remove that file completely, otherwise remove just those lines.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Hi Everyone,
After reading through BBGeek's tutorial earlier today about LVM-Thin, I was inspired to share an educational article I recently published on my blog. The article explores Mac OS X Snow Leopard Server, a remarkable operating system...
Hi @RobertKih
Good news... It is not the disk. Those EIOs come from the kernel's DMA mapping code, before the write ever reaches the drive. That's why your smart-log is clean.
This looks like a block layer bug in 7.0.14. Split bios lose their...
@fabian, in case this turns out to be related to the PCIe link retraining regression from 7.0.14-7 (https://forum.proxmox.com/threads/7-0-14-7-kernel-breaks-pci-link-training.185549/), plain lspci -v won't show the link registers. lspci -vv as...
Hi @huganega,
Good news, this lines up with what we thought was going on.
Let me pin one thing down, though. With net.ipv4.tcp_shrink_window=1 set, are the timeouts and transport disconnects actually gone, or just less frequent? I want to know...
Coincidentally we just finished and published on article on this topic!
https://forum.proxmox.com/threads/why-lvm-thin-cannot-be-shared-storage-in-proxmox.186446/
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Hi Everyone,
Every few months someone asks some version of "why can't I use LVM-thin on my shared SAN LUN?" Thick LVM works fine as shared storage, but has no native snapshots. LVM-thin has snapshots but is local-only... it's natural to wonder...
Hey @huganega , any updates from the weekend run? How are things holding up?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
The design is what worries me. Disks owned by a dummy VMID and moved between VMs by editing configs through the API. Clever, but it does not hold up when things fail.
Snapshots: that endpoint is a copy, not a snapshot. It won't give you a chain...
@rbremer, another AI-generated driver... They've been coming in droves lately. It even modifies the PVE source files!
The problem with most AI-generated integrations is that they sound convincing, are thoroughly documented, and are subtly broken...
@rbremer discussing CSI is a big conversation of its own and deserves a separate thread, but for future readers: which CSI driver is this?
Separate from the driver: this type of PVE/K8s combination works, but it isn't reliable. Proxmox tracks...
Intriguing. Nothing in your data points to a root cause, and it doesn't look like the Dell. Our best guess is a Linux issue.
That said, we run a lot of iSCSI with PVE in the field and haven't seen any issues at customer sites. This suggests...
You've got it. That's exactly why SUSE put OCFS2 on corosync, kernel DLM and Pacemaker. One membership, one fencing authority.
As for doing the same on PVE... someone still has to pay to develop, debug, and support it. Not my circus not my...