>>1) (Already asked here two times, but no answer yet)
>>When primary goes down (for example hard disk crash) and secondary gots
rebooted after that
>>(for example power loss), it hangs and waits for the old primary. So I
absolutely MUST NOT
>>reboot the secondary when the primary is gone.
>>When one node is gone, there is no more high availability, but why is
there NO availability when
>>I have to reboot the secondary without the primary???
>if you ask drbdsetup for some options you get e.g.
>-k|--skip-sync] [-s|-tl-size val] [.-c|--connect-int
>the skip-sync does what is says - when its in your drbd.conf it skips the
sync
>post reboot.
Me was wrong - forget connect-int, search 4 : wait_connect [-t|--time val]
Michael Appeldorn
>>When primary goes down (for example hard disk crash) and secondary gots
rebooted after that
>>(for example power loss), it hangs and waits for the old primary. So I
absolutely MUST NOT
>>reboot the secondary when the primary is gone.
>>When one node is gone, there is no more high availability, but why is
there NO availability when
>>I have to reboot the secondary without the primary???
>if you ask drbdsetup for some options you get e.g.
>-k|--skip-sync] [-s|-tl-size val] [.-c|--connect-int
>the skip-sync does what is says - when its in your drbd.conf it skips the
sync
>post reboot.
Me was wrong - forget connect-int, search 4 : wait_connect [-t|--time val]
Michael Appeldorn