OK, here is a recipe to see this problem. I hope all the
steps are here!
(0) Install drbd8-utils and heartbeat.
(1) Create a fake disk
dd if=/dev/zero of=drbd_disk count=1M bs=1
losetup /dev/loop0 ./drbd_disk
(2) Create /etc/drbd.conf. I used:
global {
usage-count yes;
}
common {
protocol C
Hi, I am now trying to come up with a simple recipe that
will enable you to reproduce the problem. However, let
me just point out that the current jaunty heartbeat sources
has
./resources/OCF/drbd: DRBD_STATE=$(do_drbdadm state $RESOURCE)
which results in the mentioned problematic output using
Hi Andres,
> So you are setting up MySQL with DRBD.
the service I'm starting is not mysql, but otherwise it is essentially
the same. Since the drbd disk isn't even considered for mounting, due
to error output from drdbadm, it probably doesn't matter what service
is started.
> I'll try to reprod
