[Debian-ha-maintainers] Bug#1054326: Bug#1054326: Can't start golbal heartbeat when drbd device is on top LVM device

[Daniel Smolik]

I completely  agree, but when it is on md device then is UUID visible on 
both nodes too. My guess is  that name  of LVM  device is longer than md 
or drbd device.  And I looked  to source code and start heartbeat failed

here: in op_start.c

  if (!(od->od_flags & O2CB_DEVICE_FOUND)) {
                 tcom_err(ret, "%s", od->od_uuid);
                 goto bail;
         }

It is only testing device and for final solution isn't  local heartbeat 
possible. In o2cb is not possible specify device where start heartbeat.






Dne 22. 10. 23 v 13:37 Valentin Vidic napsal(a):
> On Sun, Oct 22, 2023 at 12:11:19PM +0200, Daniel Smolik wrote:
>> Yes no problem. There it is.
> Thanks. My best guess is that the problem happens because the region
> UUID is visible on both drbd and the lower device, so the global
> heartbeat might work if drbd device is selected first (for example in
> the case of md).
>
> Since I don't know if it possible to specify the device directly, your
> best bet now is probably to use the local heartbeat mode (that should
> work without the regions being specified).
>