bbgeek17's latest activity
-
bbgeek17 replied to the thread Proxmox PVE will crash out when Win Server 2025 and MS SQL 2025 is used..Hi @eatonjb, welcome to the forum. The first thing I would check is the system log:journalctl. There may be some clues there. If the customer has to manually power-cycle the server, that may indicate that there are messages on the console. If a... -
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hi @mira, I’ll check with the developers on the current status. They are currently working through a number of existing deliverables, so this is in the queue but is not something I expect to be completed immediately. Since we have not seen this...
-
bbgeek17 replied to the thread qcow2 file is bigger as hdd config.You could try virt-sparsify on your file to see if that helps. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 reacted to alexskysilk's post in the thread [TUTORIAL] Why LVM-Thin Cannot Be Shared Storage in Proxmox with
Like.
@bbgeek17 no disagreement. I was simply pointing out that the premise that a full node fence is required isnt necessarily true for the proposed solution to work. I'm not suggesting its easy, not fraught with gaping holes, probably too slow to be... -
bbgeek17 replied to the thread Error when trying to remove a previously physically removed node.Sorry, I missed the forum name - that documentation/procedure is for the PVE Cluster. If you have collection of single nodes under PDM, take a look at this thread: https://forum.proxmox.com/threads/how-to-remove-node-from-remotes.163437/...
-
bbgeek17 replied to the thread Error when trying to remove a previously physically removed node.Hi @bishoptf , Have you checked the cluster guide? https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_remove_the_cluster_node Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread Feature idea: saferemove mode to skip forced zero-write (blkdiscard --zeroout) on storage that guarantees zero-after-discard (e.g. NVMe DLFEAT).Hi Mike, It's a good idea, but it's worth noting that discard has a rough history. SATA TRIM often didn't guarantee zeros, a bunch of drives corrupted data on queued TRIM and are still on the kernel blacklist, and arrays have been all over the...
-
bbgeek17 replied to the thread Proxmox Virtual Environment now available for 64-bit ARM (arm64)!.A new article for ARM system users covering performance troubleshooting Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 posted the thread [TUTORIAL] PVE 9.2 arm64 on ASUS GX10 (GB10): SoC throttled to 20 W, affecting performance in Proxmox VE: Installation and configuration.Now that the system is "stable" after dealing with the black screen and the watchdog resets, we've started looking at performance. Our first look at storage performance was absolutely terrible. And after some head scratching, learning a bit more...
-
bbgeek17 replied to the thread [TUTORIAL] Why LVM-Thin Cannot Be Shared Storage in Proxmox.Hi @alexskysilk , you know I love a good bash loop, but ACL toggling is vendor-specific. It often only gates new logins, so an established session keeps writing until the target decides to drop it, and whether it does that on revoke is up to the...
-
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...