Search results

It does not work on latest release proxmox 7.2-4. Not to mention that after manually patching, a lot of errors show up regarding Cloudinit.pm when trying to regenerate a cloudinit drive for a VM. This is reffering to: sub configdrive2_gen_metadata { Password for windows administrator is never...

There is no way to recover anything. The bug seems similar, because when running backups I/O usage and resource usage is probably higher than normal, though we did not ran any backups but we did started a remote rsync restoration to a VM , this caused high I/O and other resource usage which led...

Can't be restored, disks exists but partition table was wiped. No backup was running, only what I first specified in the first post . It should get more priority because this is very alarming and can happen in a production environment.

That is what I also thought. Now, the problem is that we are afraid to try again because we have no idea what else could happen, as there are more VMs running inside this cluster, if you have any other idea what should we check for please let us know.

Hello, Thank you for your explanation. Does what you mention applies if this specific VM was create like 1 month ago? Was shutdown, started/rebooted several times before starting the migration? What I mean is that the changes were surely commited to the disks as those were created long time...

Hello, We are running multiple VMs in the following environment: proxmox cluster with ceph storage - block storage - all osds are enterprise SSDs (RBD pool 3 times replicated). ceph version: 15.2.11 All nodes inside the cluster have exactly this following version...

how about lacp? if the switches support it?

I personally do not use or recommend the use of this variant in some important production cluster.

I agree, but in total, those are still 3.

https://pve.proxmox.com/wiki/High_Availability

You need 3 servers(nodes). You can spread all 12 VMs on these 3 nodes as you wish. You do not need 2 clusters.

To have a working cluster and HA you need at least 3 nodes and you will be able to do what you need. All nodes within the same cluster (one cluster).

you need at least three nodes.

multicast issues? I would check networking

I believe he was talking about the storage itself, not the drive. You can see and change that from Datacenter -> Storage. The ceph storage, when editing, should have the option KRBD there. Though some of us might notice performance difference, thats why I will wait till they will fix this issue.

What is your ceph version and are you using bluestore? Have a look at osd_memory_target which I believe in newest versions it defaults to 4GB. I do believe that the OSDs should not eat more memory than they are told to, correct me if I'm wrong.

Post your networking config. I see loss on your outputs, so things are not fine.

I'd use network one for the proxmox cluster(corosync), network 2 as you, network 3 and 4 ceph public/private.

We had the same issue on 2 clusters, on all newly fresh installed nodes. As above stated, wait until the time catches up with the timestamp in the rrd database and the errors will be gone

We expect it to work with krbd in the nearby future aswell, as some of us might see performance difference when using krbd.