Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 2004-09-24T15:30:43,
Shane Swartz <sswartz at ucar.edu> said:
> I'm running DRBD 0.7.4 and Heartbeat 1.2.3 on a cluster running Debian
> 2.4. I experience the problem when I simulate a failure on the primary
> node by executing a reboot while writing data to the file system
> controlled by DRBD. The failover node takes control of all resources as
> it should during the reboot, but once the primary node comes up
> heartbeat on the failover is killed causing the primary node to take
> control again. I have auto_failback set to off.
This sounds like the regular scenario "Normal shutdown but network
stopped before drbd is + no fencing". You really shouldn't be doing
this. Please make sure drbd + heartbeat are stopped before the network
is shutdown.
Sincerely,
Lars Marowsky-Brée <lmb at suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company