<br><font size=2 face="sans-serif">Hi!</font>
<br><font size=2 face="sans-serif">I have a cluster with Sles11 HAE SP1
x86_64 running drbd and pacemaker. Replication link is two direct
1GBit links bonded with bonding mode balance-rr</font>
<br><font size=2 face="sans-serif">The system is in a very interesting
state, that will lead straight into desaster if a failover should occur.
The master Node has the secondary as unknown with blocks out of sync, while
the secondary thinks everything is OK. if a failover occurs, it happily
comes up with stale data. I have no idea what could cause this.</font>
<br><font size=2 face="sans-serif"> Novell support is already involved,
but they have not yet come back with a solution since last wednesday. Any
Ideas</font>
<br><font size=2 face="sans-serif">Node1:~ # cat /proc/drbd</font>
<br><font size=2 face="sans-serif">version: 8.3.10 (api:88/proto:86-96)</font>
<br><font size=2 face="sans-serif">GIT-hash: 5c0b0469666682443d4785d90a2c603378f9017b
build by phil@fat-tyre, 2011-01-28 12:17:35</font>
<br><font size=2 face="sans-serif"> 0: cs:Connected ro:Primary/Secondary
ds:UpToDate/UpToDate C r-----</font>
<br><font size=2 face="sans-serif"> ns:2015223 nr:32 dw:2015228
dr:896547611 al:40 bm:12 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0</font>
<br><font size=2 face="sans-serif"> 1: cs:Connected ro:Primary/Secondary
ds:UpToDate/UpToDate C r-----</font>
<br><font size=2 face="sans-serif"> ns:2022882 nr:4281 dw:2027129
dr:1413273405 al:38 bm:20 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0</font>
<br><font size=2 face="sans-serif"> 2: cs:Connected ro:Primary/Secondary
ds:UpToDate/DUnknown C r-----</font>
<br><font size=2 face="sans-serif"> ns:12558893 nr:63340 dw:28009675
dr:1503787133 al:3204 bm:1060 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:1285512</font>
<br><font size=2 face="sans-serif">Node1:~ # ssh node2 cat /proc/drbd</font>
<br><font size=2 face="sans-serif">version: 8.3.10 (api:88/proto:86-96)</font>
<br><font size=2 face="sans-serif">GIT-hash: 5c0b0469666682443d4785d90a2c603378f9017b
build by phil@fat-tyre, 2011-01-28 12:17:35</font>
<br><font size=2 face="sans-serif"> 0: cs:Connected ro:Secondary/Primary
ds:UpToDate/UpToDate C r-----</font>
<br><font size=2 face="sans-serif"> ns:0 nr:2015223 dw:2015223
dr:143334132 al:0 bm:12 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0</font>
<br><font size=2 face="sans-serif"> 1: cs:Connected ro:Secondary/Primary
ds:UpToDate/UpToDate C r-----</font>
<br><font size=2 face="sans-serif"> ns:0 nr:2022882 dw:2022882
dr:143334132 al:0 bm:16 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0</font>
<br><font size=2 face="sans-serif"> 2: cs:Connected ro:Secondary/Primary
ds:UpToDate/UpToDate C r-----</font>
<br><font size=2 face="sans-serif"> ns:0 nr:12558753 dw:12558753
dr:716687192 al:0 bm:1045 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0</font>
<br><font size=2 face="sans-serif">node1:~ # corosync-cfgtool -s</font>
<br><font size=2 face="sans-serif">Printing ring status.</font>
<br><font size=2 face="sans-serif">Local node ID 16885952</font>
<br><font size=2 face="sans-serif">RING ID 0</font>
<br><font size=2 face="sans-serif"> id
= 192.168.1.1</font>
<br><font size=2 face="sans-serif"> status =
ring 0 active with no faults</font>
<br><font size=2 face="sans-serif">RING ID 1</font>
<br><font size=2 face="sans-serif"> id
= 10.73.50.11</font>
<br><font size=2 face="sans-serif"> status =
ring 1 active with no faults</font>
<br><font size=2 face="sans-serif"><br>
</font><font size=3 color=#5f5f5f>Mit freundlichen Grüßen / Best Regards<br>
<br>
Robert Köppl<br>
<br>
Systemadministration<br>
<b><br>
KNAPP Systemintegration GmbH</b><br>
Waltenbachstraße 9<br>
8700 Leoben, Austria <br>
Phone: +43 3842 805-910<br>
Fax: +43 3842 82930-500<br>
robert.koeppl@knapp.com <br>
www.KNAPP.com <br>
<br>
Commercial register number: FN 138870x<br>
Commercial register court: Leoben</font><font size=3><br>
</font><font size=3 color=#d2d2d2><br>
The information in this e-mail (including any attachment) is confidential
and intended to be for the use of the addressee(s) only. If you have received
the e-mail by mistake, any disclosure, copy, distribution or use of the
contents of the e-mail is prohibited, and you must delete the e-mail from
your system. As e-mail can be changed electronically KNAPP assumes no responsibility
for any alteration to this e-mail or its attachments. KNAPP has taken every
reasonable precaution to ensure that any attachment to this e-mail has
been swept for virus. However, KNAPP does not accept any liability for
damage sustained as a result of such attachment being virus infected and
strongly recommend that you carry out your own virus check before opening
any attachment.</font>