DRBD Connect Primary und Secondary nach Server Neuinstallation

Dieses Thema im Forum "Server Administration" wurde erstellt von sschmidt, 10. Sep. 2012.

  1. sschmidt

    sschmidt New Member

    Hallo,
    folgendes Problem:

    Immer wenn ich versuche SRV01 und SRV02 mit den übliche Befehlen
    (Secondary: drbdadm -- --discard-my-data connect r0 bzw.
    Primary: drbdadm -- --overwrite-data-of-peer primary r0) zu verbinden bekomme ich die Meldung NetworkFailure.
    Die Netzwerkkonfiguration habe ich komplett überprüft und ich kann über das entsprechende Ethernet-Device beide Server einwandfrei erreichen.

    Hier die Stati bzw. die Konfig (die auf beiden Servern gleich aussieht):

    root@srv01:~# cat /etc/drbd.conf
    # You can find an example in /usr/share/doc/drbd.../drbd.conf.example

    #include "drbd.d/global_common.conf";
    #include "drbd.d/*.res";

    global {
    usage-count no;
    }

    common {
    protocol C;
    syncer {
    rate 100M;
    }
    }

    resource r0 {

    startup {
    degr-wfc-timeout 30;
    wfc-timeout 15;
    become-primary-on srv01;
    }

    on srv01 {
    device /dev/drbd0;
    disk /dev/sda3;
    address 10.0.0.10:7789;
    meta-disk internal;
    }
    on srv02 {
    device /dev/drbd0;
    disk /dev/sda7;
    address 10.0.0.20:7789;
    meta-disk internal;
    }
    }

    SRV01:

    drbd driver loaded OK; device status:
    version: 8.3.13 (api:88/proto:86-96)
    GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@srv01, 2012-07-23 15:21:40
    m:res cs ro ds p mounted fstype
    0:r0 StandAlone Primary/Unknown UpToDate/DUnknown r----s

    SRV02:

    drbd driver loaded OK; device status:
    version: 8.3.13 (api:88/proto:86-96)
    GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@srv02, 2012-08-02 14:45:48
    m:res cs ro ds p mounted fstype
    0:r0 WFConnection Secondary/Unknown Inconsistent/DUnknown C

    Ausgabe wenn ich versuche beide zu verbinden:


    Sep 5 11:10:03 localhost kernel: block drbd0: Handshake successful: Agreed network protocol version 96
    Sep 5 11:10:03 localhost kernel: block drbd0: conn( WFConnection -> WFReportParams )
    Sep 5 11:10:03 localhost kernel: block drbd0: Starting asender thread (from drbd0_receiver [857863])
    Sep 5 11:10:03 localhost kernel: block drbd0: data-integrity-alg: <not-used>
    Sep 5 11:10:03 localhost kernel: block drbd0: max BIO size = 131072
    Sep 5 11:10:03 localhost kernel: block drbd0: drbd_sync_handshake:
    Sep 5 11:10:03 localhost kernel: block drbd0: self 0000000000000004:0000000000000000:0000000000000000:0000000000000000 bits:141322555 flags:0
    Sep 5 11:10:03 localhost kernel: block drbd0: peer EF0275BE69C06249:0000000000000004:0000000000000000:0000000000000000 bits:141322563 flags:0
    Sep 5 11:10:03 localhost kernel: block drbd0: uuid_compare()=-2 by rule 20
    Sep 5 11:10:03 localhost kernel: block drbd0: Becoming sync target due to disk states.
    Sep 5 11:10:03 localhost kernel: block drbd0: Writing the whole bitmap, full sync required after drbd_sync_handshake.
    Sep 5 11:10:03 localhost kernel: block drbd0: conn( WFReportParams -> NetworkFailure )
    Sep 5 11:10:03 localhost kernel: block drbd0: asender terminated
    Sep 5 11:10:03 localhost kernel: block drbd0: Terminating asender thread
    Sep 5 11:10:03 localhost kernel: block drbd0: bitmap WRITE of 4313 pages took 99 jiffies
    Sep 5 11:10:03 localhost kernel: block drbd0: 539 GB (141322555 bits) marked out-of-sync by on disk bit-map.
    Sep 5 11:10:03 localhost kernel: block drbd0: Connection closed
    Sep 5 11:10:03 localhost kernel: block drbd0: conn( NetworkFailure -> Unconnected )
    Sep 5 11:10:03 localhost kernel: block drbd0: receiver terminated
    Sep 5 11:10:03 localhost kernel: block drbd0: Restarting receiver thread
    Sep 5 11:10:03 localhost kernel: block drbd0: receiver (re)started
    Sep 5 11:10:03 localhost kernel: block drbd0: conn( Unconnected -> WFConnection )
     
    Zuletzt bearbeitet: 10. Sep. 2012

Diese Seite empfehlen