drbdadm secondary takes about 30 seconds to complete
johannesthoma opened this issue · 3 comments
Setting a WinDRBD resource from Primary to Secondary takes about 30 seconds to complete. This is probably because Windows treats this as a SUPRISE_REMOVAL PnP Event (like unplugging an USB stick without ejecting it first). During the 30 seconds a drbdadm status (or drbdadm anything) won't succeed because it hangs in the drbdadm seconary command.
This also applies to drbdadm down when the resource was Primary before.
Probably need to remove device from user space (only the Windows device not the DRBD device), see deveject for sample API (setup API CM_Request_Device_EjectA() function).
Currently I cannot reproduce this on my system. But this most likely also triggers a PNP_WATCHDOG_VIOLATION (also reported later on in #12) and also reported by @acidrop .
Funny how one bug can appear at various places ...
Should be fixed with rc8-13 (rc9 will be available with this fix shortly ...)