Search results

In our internal documentation, a 'just' 2 node setup is not recommended. The recommendation we do, 2 PVE servers + 1 PBS server (hardware) or something else that can act as a voting node: https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_qdevice_technical_overview In all cases we end up...

Yes I agree with fabian here, if you look at your 'read' speed that is stable, and it is scanning the full disk to find the blocks to backup which can result in parts of the backup actually writing 0 bytes and in nearly all cases itll write less then it will read. This looks normal.

@ Staff. I see the 6.17 kernel is still in the enterprise repository for PBS.. with these problems resulting in broken VM disks i'd have expected that to be pulled for now until a fix is available. Right now if I, or anyone would update in a simular situation their env blows up.

it is in my earlier message, but our main production clusters we have both 9 and 8 versions, both fully updated as of last weekend. All PBS is 4 though (4.0 with the 6.14 kernel)

Can confirm downgrading the kernel worked for us, no more hanging backups or broken vms.

Welcome to the party Do not wait finishing upgrading your PVE cluster. PBS is the problem here so either do not upgrade PBS, or 'downgrade' PBS to the 6.14 kernel. The PVE machines are not an issue here and seem to be safe to upgrade to 9. For right now in our env I have: - Disabled all...

Same issue here PBS on ZFS fully upgraded, PVE 8 and 9 (2 seperate clusters) on both sides after upgrading this weekend I woke up to a absolute shitshow this morning with vm's detached from their ceph disks, linux complaining about scsi & ext4 errors and generally a bad time. After fixing all of...

Ofcourse, https://bugzilla.proxmox.com/show_bug.cgi?id=5649 and https://bugzilla.proxmox.com/show_bug.cgi?id=5650 Hope the bug reports are enough information.

Hello, Currently vzdump on PVE has no namespace support, but instead relies on having the backup storage linked with a namespace in the storage configuration. While this is probably a perfectly fine option for some. In our case this would mean we need to connect roughly 600 storage drives to...

Hello, the above issue has still not been fixed, I did find out with the ovs devs that this is a problem with ovs which occurs when you have multiple instances (switches) running on the same machine with rstp.. Now this should just work however rstp is a 'unsupported' feature in ovs so I doubt...

Another one with the same problem. Can confirm its arp requests that are getting ignored. Can also confirm that this is specifically related to the combination of proxmox + openvswitch + rstp + ifupdown2. To dig in to this further (I really need to have this work) I set up several tests. the...