Have you tried to force the disk to primary with drbdadm primary <disk>
manually? I also give it a try with Proxmox6. I can migrate disks while the machine is stopped. If I try to migrate online I get the same error. And if I try to start a VM with disks that are "secondary" on that machine I do also get it. If I switch it manually to primary it starts. But auto-propagate is working if I for example try fdisk on the host on the according drbd-dev. Seems like it takes to long for some operations, or doesn't get triggered. Migration of vms between hosts also requires to set the second host to primary first, otherwise migration fails. Regards, Daniel On 7/15/19 11:55 AM, Denis wrote: > Il 15/07/19 11:36, Roland Kammerer ha scritto: >> On Mon, Jul 15, 2019 at 08:25:09AM +0100, Gianni Milo wrote: >>>> I run a similar 3-nodes production cluster with PVE 5.4-3 and linstor >>>> 0.9.5-1 and 0.9.2-1 witch shows the storage content >>>> >>> I'm using PVE 5.4-3 with LINSTOR 0.9.12-1 and I can reproduce same >>> problem >>> you are seeing on PVE6. Must be something that changed in linstor... >> I hope this is fixed (and released soon): >> https://github.com/LINBIT/linstor-proxmox/issues/20 >> >> Please test! > > > Hi Roland, > > now I can see the drbdstorage content but I can't start the VM on PVE6 > > I'm ready for testing, I can grant you an access to my test enviroment too > > > Denis > > > _______________________________________________ > Star us on GITHUB: https://github.com/LINBIT > drbd-user mailing list > [email protected] > http://lists.linbit.com/mailman/listinfo/drbd-user _______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
