Recent content by aaron

That was not on my list of things that could cause it :)

Can you try and specify the bridge-vids 100-120 to start at 101 in the second example? Because the dedicated interface wants to assing itself a VLAN that the bridge already has. By the way, you could also add it as it would look when you use the VLAN interface in the GUI: iface nic6 inet...

Can you please post the full /etc/network/interfaces within blocks? (or use the code format buttons of the editor. If you use the SDN, please also add the /etc/network/interfaces.d/sdn file too.

anything in the browsers console in the developer tools that might show some errors?

Some more details would be good to help you troubleshoot. Adding new memory on the fly while the VM is running is an operation that the guest OS must support as well. - What guest OS? - VM config? → qm config {vmdi} and then post the output within tags or use the buttons at the top of the editor.

Additionally, with just 3 nodes in a ceph cluster, make sure you have at least 4 OSDs in each. Because with just 2 per node, you will likely have issues if one of the OSDs fails. As then Ceph will recover the lost replicas to the only node it can -> the same. So the remaining OSD needs to...

Those are on the cheaper and slower side of consumer SSDs. They will not perform well with sustained load and the primarily sync writes that Ceph does. The recommendation for enterprise SSDs with power loss protection (PLP) is there for good reasons. Performance under sustained continuous load...

Spamcleaned... Those are, as @LnxBil mentioned, somewhat harder to notice what they advertise for on a quick read ;-)

The "create" task is definitely also logged in the task log of the guest. It might be too long ago though. But then the question is if it is still present in the syslogs/journal.

This is what we use for many internal tests, and also in the hands-on labs for our trainings. Good for functionality and behavior tests as long as performance is not a factor!

Siehst du mit rbd -p {pool} ls -l mehr als ohne dem -l Parameter? Evtl. mit einer Warnung dabei?

When VMs are getting backed up with Proxmox VE native backup methods, VMs will continue to fully run during the backup. 3rd party vendors can utilize the public backup API. Then things work the same. If they use a custom implementation under the hood, things might change. But depending on how...

Generell, wenn ein neuer Kernel mal Probleme macht, kann man einen älteren als Default Boot Option pinnen: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot_kernel_pin Um die aktuellen anzusehen: proxmox-boot-tool kernel list

Wenn die Storages auf den Nodes unterschiedlich sind, musst du das entsprechend markieren auf welchen Nodes diese verfügbar sind. Wenn du ein Storage bearbeitest oben rechts die Nodes auswählen. Per Default sind alle Storages für alle Nodes definiert. Beim Cluster Join übernimmt die neue Node...

Set it to warn, then you will see what the ideal would be, without it acting by itself. You should have something in the ballpark of 100PGs/OSD. If you have to few, it can impact performance and also recovery speed/impact in case you lose a node/OSD.