Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I would have to ask why you would want that. If you have a secondary node
coming up again, heartbeat will do no harm as it will not try to take your
unsynced resource primary (except if you use the auto_failback option).
The drbd and heartbeat startscripts normally get run as boot scripts. It is
not drbds task to worry about the heartbeat start. The processing of the
resource-scripts within heartbeat following drbd *could* be interrupted by
the drbd resource-script eg when heartbeat tries to take an inconsistent node
primary. But: as far as I know there is a bug in heartbeat which prevents it
from stopping the processing of the following scripts if one of the proceding
returns a error.
If you really need it, why don't you take heartbeat out of your runlevel and
replace it by a script which checks for a running sync and waits for it to
finish before starting heartbeat.
Regards
Stephan
Am Montag, 11. Juli 2005 14:14 schrieb Tilo Kaltenecker:
> I am using DRBD 0.7.11 and wanted DRBD to wait to finish
> syncing before Heartbeat is started (stop the boot process)
> and doesn't seem to work.
>
> cat /etc/drbd.conf:
>
> resource drbd0 {
> protocol B;
> incon-degr-cmd "halt -f";
>
> startup {
> wfc-timeout 120;
> degr-wfc-timeout 120;.
> }
>
> disk {
> on-io-error detach;
> }
>
> syncer {
> rate 100M;
> group 1;
> al-extents 257;
> }
>
> on node1 {
> device /dev/drbd0;
> disk /dev/hda3;
> address 10.1.1.10:7788;
> meta-disk internal;
> }
>
> on node2 {
> device /dev/drbd0;
> disk /dev/hda3;
> address 10.1.1.20:7788;
> meta-disk internal;
> }
> }
>
>
>
> what's wrong with the drbd.conf?
>
> thanks
>
> ~ tilo
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user