DRBD no longer working in pri/pri setup.

[proxtest]

As i posted before already, my drbd setup no longer working with pri/pri. 2 weeks ago i switched to pri/sec und have no issue since then, on sunday i switched back to pri/pri and on monday i get this email:

version: 8.3.13 (api:88/proto:86-96)
GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@sighted, 2012-10-09 12:47:51
0: cs:WFConnection rorimary/Unknown ds:UpToDate/DUnknown C r-----
ns:4496240 nr:0 dw:74066828 dr:31588880 al:5759 bm:854 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:5471788

version: 8.3.13 (api:88/proto:86-96)
GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@sighted, 2012-10-09 12:47:51
0: cs:StandAlone rorimary/Unknown ds:UpToDate/DUnknown r-----
ns:0 nr:4496240 dw:4496240 dr:1792472 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0


Both nodes are thinking they are primary, one with WFConnection state and the other with StandAlone state.

Before i switched to pri/pri on sunday it was running 2 weeks as:

version: 8.3.13 (api:88/proto:86-96)
GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@sighted, 2012-10-09 12:47:51
0: cs:Connected rorimary/Secondary ds:UpToDate/UpToDate C r-----
ns:681576328 nr:0 dw:804444808 dr:247308040 al:44804 bm:19362 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0

So i can say there is something wrong with drbd since the last updates. Maybe there was some changes in the kernel module?

2.6.32-34-pve

Now i switched back to pri/sec:

version: 8.3.13 (api:88/proto:86-96)
GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@sighted, 2012-10-09 12:47:51
0: cs:SyncTarget ro:Secondary/Primary ds:Inconsistent/UpToDate C r-----
ns:0 nr:400 dw:4496640 dr:1792776 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:8041436
[>....................] sync'ed: 0.1% (7852/7852)M
finish: 2:47:31 speed: 400 (400) want: 2,440 K/sec

Ok not be shocked, the sync speed jumps up and down, it was in the first second only.

So now back in stable pri/sec setup but HA is gone now. :-(

 

[nihilanthlnxa]

Greetings.

Proxtest, Can you put here the DRBD config file? You gave us the behavior of your DRBD, but that's not enough.

Well, show us the infrastructure and configs, if it is not too much to ask.

 

[proxtest]

Greetings.

Proxtest, Can you put here the DRBD config file? You gave us the behavior of your DRBD, but that's not enough.

Well, show us the infrastructure and configs, if it is not too much to ask.

Sorry for the delay, have stressy days at the moment. :-(

Get a timeout when i want to post my answer and after login i have to write it again! :-(
Where can i change the timeout in this forum?

This is the Global.conf
global { usage-count no; }
common {
syncer {
c-plan-ahead 20;
c-min-rate 1M;
c-max-rate 95M;
c-fill-target 2M;
verify-alg md5;
al-extents 3833;
}
handlers { out-of-sync "/usr/lib/drbd/notify-out-of-sync.sh root"; }
}

This is resource.conf

resource r1 {
protocol C;
startup {
wfc-timeout 0; # non-zero wfc-timeout can be dangerous (http://forum.proxmox.com/threads/3465-Is-it-safe-to-use-wfc-timeout-in-DRBD-configuration)
degr-wfc-timeout 60;
become-primary-on both;
}
net {
sndbuf-size 10M;
rcvbuf-size 10M;
ping-int 2;
ping-timeout 2;
connect-int 2;
timeout 5;
ko-count 5;
max-buffers 128k;
max-epoch-size 8192;
cram-hmac-alg sha1;
shared-secret "XXXXX";
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;
#data-integrity-alg crc32c; # has to be enabled only for test and disabled for production use (check man drbd.conf, section "NOTES ON DATA INTEGRITY")
}
on node1 {
device /dev/drbd0;
disk /dev/md2;
address XXXXXXX:7788;
meta-disk internal;
}
on node2 {
device /dev/drbd0;
disk /dev/md2;
address XXXXXX:7788;
meta-disk internal;
}
disk {
# no-disk-barrier and no-disk-flushes should be applied only to systems with non-volatile (battery backed) controller caches.
# Follow links for more information:
# http://www.drbd.org/users-guide-8.3/s-throughput-tuning.html#s-tune-disable-barriers
# http://www.drbd.org/users-guide/s-throughput-tuning.html#s-tune-disable-barriers
# no-disk-barrier;
# no-disk-flushes;
no-disk-flushes;
no-md-flushes;
no-disk-barrier;
}
}

My drbd status is:

version: 8.3.13 (api:88/proto:86-96)
GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@sighted, 2012-10-09 12:47:51
0: cs:Connected rorimary/Secondary ds:UpToDate/UpToDate C r-----
ns:302895976 nr:0 dw:416798608 dr:162012748 al:25319 bm:12895 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0


MY network status is:
eth1 Link encap:Ethernet Hardware Adresse
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:39563106 errors:0 dropped:0 overruns:0 frame:0
TX packets:232093544 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:11698857805 (10.8 GiB) TX bytes:335336561031 (312.3 GiB)


There are no other errors than in drbd.
Network is a gigabit network only for drbd.


Feb 1 14:40:22 node1 kernel: igb 0000:07:00.1: eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Regards.