<div>Heiko,</div>
<div>whhich machine crashes? Primary only, both?</div>
<div>I think it is primary but only in case xen VM is running on top of DRBD. You can prevent crashes by disabling TOE. Or use DRBD 8.3.2, AFAIK there should be a parameter that should help in such setups.</div>
<div>Check older posts in this list.</div>
<div> </div>
<div>Tino<br><br></div>
<div class="gmail_quote">2009/7/27 Heiko <span dir="ltr"><<a href="mailto:rupertt@gmail.com">rupertt@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br><br>
<div class="gmail_quote">
<div class="im">On Mon, Jul 27, 2009 at 2:18 PM, Martin Gombac <span dir="ltr"><<a href="mailto:martin@isg.si" target="_blank">martin@isg.si</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">In my humble opinion, drbd does't crash if you loose network connections. :-)<br>Would be a first in history.<br>
Maybe heartbeat puts both sources to primary and when they join you got split brain.<br>In this case you didn't set up heartbeat correctly.<br></blockquote></div>
<div>Hello M.,<br><br>i had some people here that confirmed a bug in protocol C that causes these crashes.<br>I also thought of heartbeat, but I now have 2 ucast devices and we still have crashes and <br>no entries in the logfile that say it does a reboot on purpose:<br>
<br>only these messages:<br><br>heartbeat[2880]: 2009/07/27_11:59:37 ERROR: glib: Unable to send [-1] ucast packet: No such device<br>heartbeat[2880]: 2009/07/27_11:59:37 ERROR: write_child: write failure on ucast eth0.: No such device<br>
<br><br><br><br>my ha config looks like this<br><br>#use_logd on<br>logfile /var/log/ha-log<br>debugfile /var/log/ha-debug<br>logfacility local0<br>keepalive 2<br>deadtime 10<br>warntime 3<br>initdead 20<br>udpport 694<br>
ucast eth0 172.17.8.201<br>ucast eth0 172.17.8.202<br>ucast eth1 172.31.0.1<br>ucast eth1 172.31.0.2<br>node xen-a1.fra1<br>node xen-b1.fra1<br>auto_failback on<br><br>haresources:<br><br>xen-a1.fra1 drbddisk::blrg xen::blrg-vm1<br>
<br><br><br>thnx a lot<br><br><br>.r<br><br></div>
<div class="im">
<blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br>Regards,<br>M.
<div>
<div></div>
<div><br><br>On 27, Jul2009, at 1:47 PM, Heiko wrote:<br><br></div></div>
<blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div></div>
<div>Hello,<br><br>i have to convince my boss that our server crashes i reported on this list are due<br>to a non exsiting dedicated line! We have all our drbd traffic routed through switches<br>and they often just crash.<br>
<br>Now I have to create a test setup to show them that when I plug the corg/shutdown the networkdevice<br>the machines tend to crash.<br>Since I dont have any spare machines I would like to use loopback devices,<br>are these supported by now? I found some list entries that say this is not supported by drbd!<br>
would this be enough to get the machines crashing?<br>We use drbd8.0 and 8.2 and have on both these crashes.<br><br><br>cheers.<br></div></div>_______________________________________________<br>drbd-user mailing list<br><a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br></blockquote><br></blockquote></div></div><br><br>_______________________________________________<br>
drbd-user mailing list<br><a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br><a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
<br></blockquote></div><br>