Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Lars, we found the "fly in the ointment" . we know why it fails, but no idea how to fix it. Take this basic setup: test1 and test2 running drbd and heartbeat. drbd is on a cross-over cable between the two. heartbeat is on the public interface. test1 is primary (for the sake of argument) unplug the public ethernet interface from test1. Nothing changes. test2 cannot become primary. it is impossible. test1 is already primary. drbd connection is active. heartbeat attempts to run a drbddisk r0 start on test2 which is physically impossible, because drbd is already running. test2 never gets the virtual ip resource (though I'm not sure why). the debug log says "success" but it doesn't actually do it. running the command manually for the virtual ip works ok though. heartbeat would need to do the following for this to work properly: 1. don't attempt to start drbd - this will never work 2. do an unmount of the drbd filesystems on test1 3. do a drbdadm secondary on test1 4. then do a drbdadm primary all on test2 I'm not even sure this is possible. Dan. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20070614/2a23c408/attachment.htm>