Hi Everybody,<br><br>We have been using DRBD 0.7.24 for very long time. But the time for upgrade has finally come. So DRBD 8.3.1 was installed and drbd.conf adjusted. However now DRBD behaves differently when primary node gets rebooted. When we were running DRBD 0.7.24 and the primary node went down the secondary one took over primary role, and when the faulty node got up it became secondary. Now when we are running DRBD 8.3.1 if primary node goes down the secondary one still takes over, but when the faulty node gets up, both nodes go in stand-alone mode breaking the cluster in pieces.<br>
<br>I guess that we made a mistake in our drbd.conf file. Could please someone advise where it is. Our configuration file is as follows:<br><br>global {<br> usage-count no;<br>}<br>resource shared {<br> protocol C;<br>
handlers {<br> pri-on-incon-degr "echo '!DRBD! pri on incon-degr' | wall ; sleep 15 ; halt -f";<br> }<br> startup {<br> wfc-timeout 1;<br> degr-wfc-timeout 1;<br> outdated-wfc-timeout 1;<br>
}<br> disk {<br> on-io-error detach;<br> }<br> net {<br> timeout 60;<br> sndbuf-size 1M;<br> connect-int 10;<br> ping-int 10;<br> max-buffers 4096;<br> max-epoch-size 2048;<br>
ko-count 4;<br> after-sb-0pri discard-younger-primary;<br> after-sb-1pri consensus;<br> after-sb-2pri disconnect;<br> }<br> syncer {<br> rate 100M;<br> al-extents 1017;<br>
}<br> device /dev/drbd0;<br> disk /dev/sda9;<br> meta-disk /dev/sda8[0];<br> on node1 {<br> address <a href="http://192.168.1.2:7790">192.168.1.2:7790</a>;<br> }<br> on node2 {<br> address <a href="http://192.168.1.3:7790">192.168.1.3:7790</a>;<br>
}<br>}<br><br>Thank you in advance,<br>Maxim Vladimirsky<br>