DRBD 9 outdated after VM cloning

robhost

Active Member
Jun 15, 2014
224
9
38
Dresden
www.robhost.de
Hi,

we've got a 3 node PVE 4 (latest tools/updates) cluster with DRBD 9.
When cloning a VM, the state is always "Outd" on the 3rd node as follows:

Code:
102:vm-123-disk-1/0  Connected(3*) Seco(node1,node3)/Prim(node2) UpTo(node3)/Outd(node1)/UpTo(node2)

On the other 2 nodes everything is ok (UpTo).

This can be solved by migrating the VM to the outdated node1. The question is, if this a real problem or not and why this happens?+
Thanks.
 
I have exactly the same problem on my nodes with PVE4 and DRBD9. Not even after cloning alone, even after a reboot of the last node.

Node 1 and 2 say: everything uptodate
Node 3 says: some disks outtodate.

Do you have a solution already? I tried several times drbdadm adjust all but it doesn't work.
 
Where did you switch to? We try it now for a few days but is crashing daily.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!