When I start drbd on a system whose peer is up and running as primary, the init script seems to just be stuck waiting for that peer to do what's already done. Check out the screenshot at http://www.fluxsoft.com/images/drbdwaiting.jpg. thewarehouse1 is primary and has already connected and is syncing one of the resources but the init script is just sitting there demanding I type yes to cancel what already did. Or am I just confused about what this script wants?
read man pages regarding degr-wfc-timeout and wfc-timeout and check them in your drbd.conf. Note: 0 means wait forever.
Oh, this bug isn't in your script; it's part of drbdadm itself, sorry.
