Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- DRBD module version: 8.3.9
- userland version: 8.3.8
- you should upgrade your drbd tools!
- DRBD module version: 8.3.9
- userland version: 8.3.8
- you should upgrade your drbd tools!
- DRBD module version: 8.3.9
- userland version: 8.3.8
- you should upgrade your drbd tools!
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 48.7825 s, 11.0 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 51.5241 s, 10.4 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 51.2448 s, 10.5 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 51.1659 s, 10.5 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 48.3632 s, 11.1 MB/s
- DRBD module version: 8.3.9
- userland version: 8.3.8
- you should upgrade your drbd tools!
- 1: State change failed: (-12) Device is held open by someone
- Command 'drbdsetup 1 down' terminated with exit code 11
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 8.59402 s, 62.5 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 8.48699 s, 63.3 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 8.73956 s, 61.4 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 8.67516 s, 61.9 MB/s
- 1+0 records in
- 1+0 records out
- 536870912 bytes (537 MB) copied, 8.74392 s, 61.4 MB/s
- global {
- usage-count no;
- }
- common {
- # transfer protocol to use.
- # C: write IO is reported as completed, if we know it has
- # reached _both_ local and remote DISK.
- # * for critical transactional data.
- # B: write IO is reported as completed, if it has reached
- # local DISK and remote buffer cache.
- # * for most cases.
- # A: write IO is reported as completed, if it has reached
- # local DISK and local tcp send buffer. (see also sndbuf-size)
- # * for high latency networks
- #
- protocol C;
- handlers {
- # what should be done in case the cluster starts up in
- # degraded mode, but knows it has inconsistent data.
- #pri-on-incon-degr "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; halt -f";
- pri-on-incon-degr "echo 'DRBD: primary requested but inconsistent!' | wall; /etc/init.d/heartbeat stop"; #"halt -f";
- pri-lost-after-sb "echo 'DRBD: primary requested but lost!' | wall; /etc/init.d/heartbeat stop"; #"halt -f";
- #pri-on-incon-degr "echo o > /proc/sysrq-trigger";
- #pri-lost-after-sb "echo o > /proc/sysrq-trigger";
- #local-io-error "echo o > /proc/sysrq-trigger";
- }
- startup {
- #The init script drbd(8) blocks the boot process until the DRBD resources are connected. When the cluster manager
- #starts later, it does not see a resource with internal split-brain. In case you want to limit the wait time, do it
- #here. Default is 0, which means unlimited. The unit is seconds.
- wfc-timeout 0; # 2 minutes
- # Wait for connection timeout if this node was a degraded cluster.
- # In case a degraded cluster (= cluster with only one node left)
- # is rebooted, this timeout value is used.
- #
- degr-wfc-timeout 120; # 2 minutes.
- }
- syncer {
- rate 100M;
- # This is now expressed with "after res-name"
- #group 1;
- al-extents 257;
- }
- net {
- # TODO: Should these timeouts be relative to some heartbeat settings?
- # timeout 60; # 6 seconds (unit = 0.1 seconds)
- # connect-int 10; # 10 seconds (unit = 1 second)
- # ping-int 10; # 10 seconds (unit = 1 second)
- # if the connection to the peer is lost you have the choice of
- # "reconnect" -> Try to reconnect (AKA WFConnection state)
- # "stand_alone" -> Do not reconnect (AKA StandAlone state)
- # "freeze_io" -> Try to reconnect but freeze all IO until
- # the connection is established again.
- # FIXME This appears to be obsoleate
- #on-disconnect reconnect;
- # FIXME Experemental Crap
- #cram-hmac-alg "sha256";
- #shared-secret "secretPassword555";
- #after-sb-0pri discard-younger-primary;
- #after-sb-1pri consensus;
- #after-sb-2pri disconnect;
- #rr-conflict disconnect;
- }
- disk {
- # if the lower level device reports io-error you have the choice of
- # "pass_on" -> Report the io-error to the upper layers.
- # Primary -> report it to the mounted file system.
- # Secondary -> ignore it.
- # "panic" -> The node leaves the cluster by doing a kernel panic.
- # "detach" -> The node drops its backing storage device, and
- # continues in disk less mode.
- #
- on-io-error pass_on;
- # Under fencing we understand preventive measures to avoid situations where both nodes are
- # primary and disconnected (AKA split brain).
- fencing dont-care;
- # In case you only want to use a fraction of the available space
- # you might use the "size" option here.
- #
- # size 10G;
- }
- }
- #
- # this need not be drbd#, you may use phony resource names,
- # like "resource web" or "resource mail", too
- #
- resource "meta" {
- device /dev/drbd0;
- meta-disk internal;
- on itfof01 {
- address 192.168.18.51:7788;
- disk /dev/sdb1;
- }
- on itfof02 {
- address 192.168.18.52:7788;
- disk /dev/md0p1;
- }
- }
- resource "data" {
- device /dev/drbd1;
- meta-disk internal;
- on itfof01 {
- address 192.168.18.51:7789;
- disk /dev/sdb2;
- }
- on itfof02 {
- address 192.168.18.52:7789;
- disk /dev/md0p2;
- }
- }
Advertisement
Add Comment
Please, Sign In to add comment