Monday, February 27, 2012

Error When Promoting DRBD Primary

I was having some issues today setting up DRBD on some new SANs. When I would try and promote one of the SANs to primary using this command:
sudo drbdadm -f primary r0

I would get this error:
0: State change failed: (-2) Need access to UpToDate data
Command 'drbdsetup 0 primary' terminated with exit code 17

Checking the status reveals:
cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
srcversion: DA5A13F16DE6553FC7CE9B2
 0: cs:Connected ro:Secondary/Secondary ds:Inconsistent/Inconsistent C r-----
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:1953460984

The reason for this is because neither server can tell if it has the correct data, so we need to invalidate one of them, so the other one thinks it is up-to-date. This is pretty simple. On the secondary server, simple use this command (replacing r0 with your resource):
sudo drbdadm invalidate r0

That's it. You can now successfully set your primary server with:
sudo drbdadm -f primary r0

Now check your status:
cat /proc/drbd

and you should see something similar to:
version: 8.3.11 (api:88/proto:86-96)
srcversion: DA5A13F16DE6553FC7CE9B2
 0: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r-----
    ns:1818624 nr:0 dw:0 dr:1819288 al:0 bm:110 lo:0 pe:48 ua:0 ap:0 ep:1 wo:f oos:1951645432
        [>....................] sync'ed:  0.1% (1905900/1907676)Mfinish: 16:47:51 speed: 32,260 (30,772) K/sec

Huzzah, success!
Posted by at
Labels: ,

20 comments:

  1. CarusoMay 24, 2012 at 9:38 AM

    No works for me....still same error !!


    # drbdadm primary r0
    0: State change failed: (-2) Need access to UpToDate data
    Command 'drbdsetup primary 0' terminated with exit code 17

    ReplyDelete
  2. chandan kumarJune 12, 2012 at 3:10 PM

    It worked for me at least. Thanks.

    ReplyDelete
  3. SergeySeptember 25, 2012 at 3:28 AM

    Thanks ! It works.

    ReplyDelete
  4. AnonymousOctober 26, 2012 at 2:54 AM

    Thanks a lot!

    ReplyDelete
  5. Pongsiri JiranggurJune 18, 2013 at 11:59 PM

    This comment has been removed by the author.

    ReplyDelete
  6. Pongsiri JiranggurJune 19, 2013 at 12:00 AM

    Thank you very much It works now.

    ReplyDelete
  7. UnknownJuly 4, 2013 at 5:27 AM

    Thank you!

    ReplyDelete
  8. AnonymousJuly 16, 2013 at 7:32 AM

    lifesaver; thank you :)

    ReplyDelete
  9. AnonymousSeptember 6, 2013 at 11:47 AM

    yes it works !

    ReplyDelete
  10. AnonymousSeptember 16, 2013 at 1:18 PM

    Thank you, it worked for me.

    ReplyDelete
  11. Eko DidikOctober 27, 2013 at 12:52 PM

    Option -f is unknown. Instead, use this:
    $ drbdadm --force primary r0

    ReplyDelete
  12. Peter PriskasNovember 18, 2013 at 1:41 PM

    Thanks! Worked for me also.

    ReplyDelete
  13. RcharlesDecember 17, 2013 at 6:10 PM

    Thanks!

    ReplyDelete
  14. AnonymousJanuary 7, 2015 at 10:21 AM

    Thanks it worked !

    ReplyDelete
  15. AnonymousJune 19, 2015 at 12:29 PM

    Thank you

    ReplyDelete
  16. AnonymousDecember 12, 2015 at 4:38 AM

    drbdadm invalidate drbd0
    0: State change failed: (-11) Device is diskless, the requested operation requires a disk

    ReplyDelete
  17. Tshering WangdiJanuary 11, 2016 at 2:07 AM

    I am not able to up my resource, still with the same issue

    ReplyDelete
  18. Tshering WangdiJanuary 11, 2016 at 2:10 AM

    When I run drbdadm up r0, I get
    open(/dev/sdb) failed: device or resource busy
    Operation cancelled.
    command 'drbdmeta 0 v08 /dev/sdb internal apply-al' terminated with exit code 20

    ReplyDelete
  19. AnonymousAugust 23, 2017 at 4:11 AM

    Disable SElinux and restart. It worked for me

    ReplyDelete

Subscribe to: Post Comments (Atom)