[DRBD-user] Replication problems constants with DRBD 8.3.10

cesar brain at click.com.py
Sat Jun 29 05:34:50 CEST 2013

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hi guys

can anybody help me ????
I will be very grateful if anyone can help me

*Mr. Lars Ellenberg tell me that:*
"With special purpose built fencing handlers,
we may be able to fix your setup so it will freeze IO during the
disconnected period, reconnect, and replay pending buffers,
without any reset."

Note.- I believe that the problem is my NIC Realtek, as soon as I can i will
change it for Intel,

But for now i like to know how apply this change?, 
And since I am not an experienced in DRBD, I wish someone would show me how
it should be finally the
global_common.conf   or  *.res configuration files.

*This is my actual configuration with DRBD 8.4.2 Version:*
*global_common.conf file:*

global {
        usage-count yes;
        # minor-count dialog-refresh disable-ip-verification
}

common {
        protocol C;

        handlers {
                pri-on-incon-degr
"/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
                pri-lost-after-sb
"/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
                local-io-error "/usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger ;
halt -f";
                # fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
                split-brain "/usr/lib/drbd/notify-split-brain.sh
some-user at my-domain.com";
                out-of-sync "/usr/lib/drbd/notify-out-of-sync.sh
some-user at my-domain.com";
                # before-resync-target
"/usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15 -- -c 16k";
                # after-resync-target
/usr/lib/drbd/unsnapshot-resync-target-lvm.sh;
        }

        startup {
                # wfc-timeout degr-wfc-timeout outdated-wfc-timeout
wait-after-sb
                wfc-timeout 30; degr-wfc-timeout 20; outdated-wfc-timeout
15;
        }

        options {
                # cpu-mask on-no-data-accessible
                cpu-mask 0;
        }

        disk {
                # size max-bio-bvecs on-io-error fencing disk-barrier
disk-flushes
                # disk-drain md-flushes resync-rate resync-after al-extents
                # c-plan-ahead c-delay-target c-fill-target c-max-rate
                # c-min-rate disk-timeout
                on-io-error detach; al-extents 3389; resync-rate 75M;
        }

        net {
                # protocol timeout max-epoch-size max-buffers
unplug-watermark
                # connect-int ping-int sndbuf-size rcvbuf-size ko-count
                # allow-two-primaries cram-hmac-alg shared-secret
after-sb-0pri
                # after-sb-1pri after-sb-2pri always-asbp rr-conflict
                # ping-timeout data-integrity-alg tcp-cork on-congestion
                # congestion-fill congestion-extents csums-alg verify-alg
                # use-rle
                sndbuf-size 0; no-tcp-cork; unplug-watermark 16; max-buffers
8000; max-epoch-size 8000;
                #Verificacion de replicacion online:
                data-integrity-alg md5;
                #Verificacion de datos en disco online:
                verify-alg sha1;
        }
} 

*r0.res file:*
resource r0 {

  protocol C;

  startup {
    #wfc-timeout  15;
    #degr-wfc-timeout 60;
    become-primary-on both;
  }

  net {
    #cram-hmac-alg sha1;
    #shared-secret "my-secret";
    allow-two-primaries;
    after-sb-0pri discard-zero-changes;
    after-sb-1pri discard-secondary;
    after-sb-2pri disconnect;
  }

  on kvm5 {
    device /dev/drbd0;
    disk /dev/sda3;
    address 10.2.2.50:7788;
    meta-disk internal;
  }

  on kvm6 {
    device /dev/drbd0;
    disk /dev/sda3;
    address 10.2.2.51:7788;
    meta-disk internal;
  }
}

*r1.res file:*
resource r1 {
  protocol C;
  startup {
    #wfc-timeout  15;
    #degr-wfc-timeout 60;
    become-primary-on both;
  }
  net {
    #cram-hmac-alg sha1;
    #shared-secret "my-secret";
    allow-two-primaries;
    after-sb-0pri discard-zero-changes;
    after-sb-1pri discard-secondary;
    after-sb-2pri disconnect;
  }
  on kvm5 {
    device /dev/drbd1;
    disk /dev/sdb3;
    address 10.2.2.50:7789;
    meta-disk internal;
  }
  on kvm6 {
    device /dev/drbd1;
    disk /dev/sdb3;
    address 10.2.2.51:7789;
    meta-disk internal;
  }
}

Best regards
Cesar




--
View this message in context: http://drbd.10923.n7.nabble.com/Replication-problems-constants-with-DRBD-8-3-10-tp17896p17981.html
Sent from the DRBD - User mailing list archive at Nabble.com.



More information about the drbd-user mailing list