Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Roberto and all :-) > Do you mean LVL or LVM-thin ? This is my storage-plugin: drbdmanage.storage.lvm.Lvm I changed it from the default before creating drbdmanage cluster > >> So when I create a VM on node1, for example, could happen that the resource >> is allocated on node2 and i get a diskless resource on node1, but this >> not seem to be a problem. > It is, if it is not intended for pve1 to be a satellite node. Diskless > is not a normal condition. I think is normal because sometime works and because, if I have a cluster of x nodes and set redundancy of 2, the node where I create the VM may not have the physical LV (because it has less free space, for example). Then the system need a diskless instance to connect to other nodes. To avoid this, the proxmox storage plugin should pass a parameter to drbdmanage and tell to assign resource on the node where the VM is. Or the user shoud be so smart enough to create the VM on the node with more free space :-) I tried this too but I got same results > >> The problem is restoring adn creating VMs, > I had a similar problem few days ago, try the workaround that Yannis > provided me on this list: > > http://lists.linbit.com/pipermail/drbd-user/2017-March/023108.html I read it, but I noticed no difference creating on primary drbdmanage node > > It seems that restore is being attempted and fails because it is > Diskless (no backing device) Sometime succedeed with diskless instance > >> 2) restoring a VM on pve215 > What is the difference between 1) and 2) ? If you tried 2 after 1), it > seems that storage is still locked because of former failed attempt. Yes, tried some time after 1) Do you know how to see and remove storage lock? Thank you, Den