Here's my drbd.conf<br><br>resource "res1" {<br> protocol C;<br> startup {<br> wfc-timeout 0;<br> degr-wfc-timeout 120;<br> }<br>
disk {<br> on-io-error detach;<br> }<br> net {<br> allow-two-primaries;<br> }<br> syncer {<br> rate 15M;<br> }<br> on "<a href="http://machine1systems.com/" target="_blank">machine1systems.com</a>"<br>
{<br> device /dev/drbd0;<br> disk /dev/sdd;<br> address <a href="http://192.168.30.12:7788/" target="_blank">192.168.30.12:7788</a>;<br> meta-disk internal;<br>
}<br> on "<a href="http://machine2.systems.com/" target="_blank">machine2.systems.com</a>"<br> {<br> device /dev/drbd0;<br> disk /dev/sde;<br> address <a href="http://192.168.30.14:7788/" target="_blank">192.168.30.14:7788</a>;<br>
meta-disk internal;<br> }<br>}<br><br>service drbd start<br>drbdadm adjust res1(on both sides)<br>drbdadm primary res1(on both sides)<br><br>Then <b>on local primary side</b>,<br>pvcreate /dev/drbd0<br>
vgcreate drbdtest /dev/drbd0<br>
lvcreate -n drbdlv1 -L 50M drbdtest<br clear="all"><br>Then,on <b>remote primary side</b>,I took snapshot <br>lvcreate -S -n snap_drbdlv1 -L 50M /dev/drbdtest/drbdlv1<br><br>I am using 'drbd-8.3.0' on 'CentOS 2.6.18-92.el5' machines.<br>
<br><b>My problem</b><br>I tested above similar scenarios like above,I got split brain error at different intervals.<br><br>like first time I got it after 10 minutes,so using <a href="http://www.drbd.org/users-guide/s-resolve-split-brain.html,I">http://www.drbd.org/users-guide/s-resolve-split-brain.html,I</a> recovered from it.<br>
<br>Then when I tested I got split brain after 30 minutes(though no operation was going on @ that time,I am closely watching /var/log/messages),then after recovery I got it after 1 hour and so on.<br><br>So I am totally confused @ exact event of split brain.Though I am doing any IO,I got it sometimes.<br>
I am not using any shared file system at the moment.It might be required only if I want that level of concurrency.<br>---------------------------------<br>Thanks and Regards,<br>Himanshu Padmanabhi<br><br>