[DRBD-user] secundary not finish synchronizing

Ricky Gutierrez xserverlinux at gmail.com
Thu Feb 8 21:52:10 CET 2018


2018-02-08 7:28 GMT-06:00 Lars Ellenberg <lars.ellenberg at linbit.com>:

Hi Lars

> And your config is?

resource zimbradrbd {
    protocol C;
    # DRBD device
    device /dev/drbd0;
    # block device
    disk /dev/hamail/opt;
    meta-disk internal;

syncer {

rate 40M;

    }

net {

        allow-two-primaries;
after-sb-0pri discard-zero-changes;
        after-sb-1pri discard-secondary;
        after-sb-2pri disconnect;

    }

startup {
become-primary-on both;

}

    on node-01.domain.nl {
        # IP address:port
        address 192.168.20.91:7788;
    }
    on node-02.domain.nl {
        address 192.168.20.92:7788;

    }

}


> And you logs say?

Feb  5 13:45:29 node-01 kernel: drbd zimbradrbd: conn( WFConnection ->
Disconnecting )
Feb  5 13:45:29 node-01 kernel: drbd zimbradrbd: Discarding network
configuration.
Feb  5 13:45:29 node-01 kernel: drbd zimbradrbd: Connection closed
Feb  5 13:45:29 node-01 kernel: drbd zimbradrbd: conn( Disconnecting
-> StandAlone )
Feb  5 13:45:29 node-01 kernel: drbd zimbradrbd: receiver terminated
Feb  5 13:45:29 node-01 kernel: drbd zimbradrbd: Terminating drbd_r_zimbradr
Feb  5 13:45:29 node-01 kernel: block drbd0: disk( UpToDate -> Failed )
Feb  5 13:45:29 node-01 kernel: block drbd0: 4622 MB (1183159 bits)
marked out-of-sync by on disk bit-map.
Feb  5 13:45:29 node-01 kernel: block drbd0: disk( Failed -> Diskless )
Feb  5 13:45:29 node-01 kernel: drbd zimbradrbd: Terminating drbd_w_zimbradr



Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: peer( Secondary ->
Unknown ) conn( Connected -> Disconnecting ) pdsk( UpToDate ->
DUnknown )
Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: ack_receiver terminated
Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: Terminating drbd_a_zimbradr
Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: Connection closed
Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: conn( Disconnecting
-> StandAlone )
Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: receiver terminated
Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: Terminating drbd_r_zimbradr
Feb  5 14:53:52 node-01 kernel: block drbd0: disk( UpToDate -> Failed )
Feb  5 14:53:52 node-01 kernel: block drbd0: 0 KB (0 bits) marked
out-of-sync by on disk bit-map.
Feb  5 14:53:52 node-01 kernel: block drbd0: disk( Failed -> Diskless )
Feb  5 14:53:52 node-01 kernel: drbd zimbradrbd: Terminating drbd_w_zimbradr



>
> As is, I can only take an (educated) wild guess:
>
> Do you have no (or improperly configured) fencing,

i don't have.

> and funky auto-resolve policies configured,
> after-split-brain ... discard-secondary maybe?



>
> Configuring automatic after-split-brain recovery policies
> is configuring automatic data loss.
>
> So if you don't mean that, don't do it.
>

I am not an expert in drbd, but with the configuration that I have
according to the documentation, should not this situation happen, or
am I wrong?

thank, I wait your answer




-- 
rickygm

http://gnuforever.homelinux.com


More information about the drbd-user mailing list