Finaly I have found the root cause of this problem!
At boot time the device mapper create mapping of logical volume on top of drbd device linked to the backing device, but it occure before drbd service startup. After this drbd cannot open exclusively the backing device resource. If I remove the...
After a reboot the DBRB comes up with Connected Diskless/Diskless status.
About the environment:
This drbd resource normaly used as a block storage for lvm, which configured as an (shared lvm) storage to a proxmox ve 5.3-8 cluster. On top of drbd block device an lvm configured, but on drbd...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.