Search results

Worked like a charm, thank you very much again for the awesome support :)

I can check that easily, we don't have that many volumes and I'm already pretty sure we never used the "backup" storage.

Thank you for the quick and useful help, this explains it of course. However this leaves me with another issue: Is there a way to remove one of the storages without removing the data? We're not using the "backup" storage so it could be deleted, but it shows all the data that is in the "vg0"...

Hello Dominik, yes of course. I have verified storage.cfg is the same on all nodes so I'm only posting it once: dir: local path /var/lib/vz content images,rootdir,vztmpl,iso maxfiles 0 shared 0 lvm: vg0 vgname vg0 content rootdir,images shared 0 lvm: backup...

Hello, I'm running a PVE 5.3-9 cluster without any shared filesystem (ceph, nfs, etc) but just a single device in LVM on each node, actually it should be pretty much default config. I want to offline migrate a lxc container from one node to another and this is what I keep getting...

Not sure if a shutdown hook would be of help here as it breaks with the "ip link del" command being issued and we found nothing we could do to get it running again besides recreating the bridge and everything connected to it.

Nah, nothing to do with the patch, my colleague found out that this is expected behaviour of the "ip" tool and nothing to do with Proxmox. When the VM/CT is shutdown a "ip link del dev $veth" is issued and this sets the bridge mtu to the mtu of the underlying physical interface, in our case...

So far I have only noticed it on shutdown or better on every shutdown as it is 100% reproducible. Here is one of my confs, it is for a lxc container but I also tested with a VM and it didn't make a difference. I'm not using pve-firewall ie. it is still in defaultconfig as it was after the pve...

Hello PVE-Community, I recently setup a three node cluster and I have this weird issue where the shutdown of a VM or CT changes the MTU of the bridge that is used for communication between VM/CTs and also for the cluster link. The MTU is changed to whatever is configured at the primary...