bbgeek17's latest activity
-
bbgeek17 replied to the thread [SOLVED] 3rd party scripts question.Hi @300cpilot, There is no official place to post third-party scripts. In this context, "official" generally implies that the material is endorsed or supported by someone in an authoritative capacity. Proxmox cannot reasonably endorse or support... -
bbgeek17 reacted to LnxBil's post in the thread LVM snapshot-as-volume-chain: newly created QCOW2 disks can expose stale data with
Like.
Another AI Slop post .... please, use the search function, this is known and can easily be fixed, e.g. in this post... -
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Ok @huganega , I think we've figured this out. It takes a combination of things to trigger: - A link that's "fast" (i.e., 25GbE) relative to your CPU (Skylake or Cascade Lake) - A backup load running at full queue depth - An array that doesn't...
-
bbgeek17 replied to the thread Idempotence of ansbile modules.A few comments about your observations: There is absolutely no "valid DNS name" requirement for a VM name in the PVE, cluster or solo. This is Ansible creator's choice, not Proxmox's. A clone creates an identical copy of a VM, resizing a disk...
-
bbgeek17 replied to the thread Idempotence of ansbile modules.You should by all means discuss any concerns you have with PVE directly, either with Proxmox or a reseller during the pre-sales process. There is nothing inherently impossible about changing software architecture. Whether a particular change...
-
bbgeek17 replied to the thread [TUTORIAL] Why LVM-Thin Cannot Be Shared Storage in Proxmox.Hi @delltech1, welcome to the forum. I'm glad you found the post useful. Your continued promotion of your AI plugin here and elsewhere motivated me to share it, because what you're promoting corrupts data. This is a clear example of how rapid...
-
bbgeek17 replied to the thread Idempotence of ansbile modules.A VM name/label is not treated as a unique identifier in PVE, or, for example, in OpenStack. The VM ID is the actual identifier. As an example, nothing in the PVE API uses the VM name or label as an addressable identifier. API operations use the...
-
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hi Werner, That's a solid advice. recv_from_iscsi_q=Y moves the receive path onto its own worker instead of running inline. If the problem is in the area where we think it is, this workaround should avoid the bug! I didn't recommend it because...
-
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hi Werner, Thanks for the confirmation. I think this points squarely at Linux kernel behavior, not the array or the fabric. Slow storage makes it a lot easier to hit, but it isn't the cause, IMHO. We have filed it in our dev queue for tracking...
-
bbgeek17 reacted to UdoB's post in the thread Configure a Fibre Channel LUN as a directory in a cluster. with Like.
In my $dayjob I have FC storage, very similar like yours (including multipath), coming from off-site. ( 3-2-1 ) I use that one as a secondary independent backup destination, as a directory storage to put vzdump-based backups on it. Limiting...
-
bbgeek17 replied to the thread WARNING: drivers/iommu/dma-iommu.c:1953 at dma_iova_link.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 -...
-
bbgeek17 replied to the thread PBS vs Veeam B&R Proxmox Plugin - QEMU live snapshot implementation & shared LVM storage.@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...
-
bbgeek17 reacted to alma21's post in the thread free Starwind x Proxmox SAN storage plugin with Like.
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...
-
bbgeek17 replied to the thread Configure a Fibre Channel LUN as a directory in a cluster..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...
-
bbgeek17 replied to the thread [SOLVED] Pinning vCPU causes 100% cpu pressure stall, using isolcpus.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...
-
bbgeek17 replied to the thread PBS vs Veeam B&R Proxmox Plugin - QEMU live snapshot implementation & shared LVM storage.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...
-
bbgeek17 replied to the thread pve8to9 upgrade warning.Just the conflicting line Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread pve8to9 upgrade warning.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 -...
-
bbgeek17 reacted to Tmanok's post in the thread [TUTORIAL] How to install Mac OS X Snow Leopard (10.6) on PVE 8-9 with Like.
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...
-
bbgeek17 replied to the thread WARNING: drivers/iommu/dma-iommu.c:1953 at dma_iova_link.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...