<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'>Hi Cesar,<br><br>I'm running DRBD from Ubuntu 12.10 on two standalone servers. I'm using two software RAIDs(6 and 1) with DRBD over top, and exposing the DRBD volumes over iSCSI to Citrix XenServer.<br><br>The sync network are two straight cable e1000's.<br><br>include "drbd.d/global_common.conf";<br># include "drbd.d/*.res";<br><br>resource iscsi.target.0 {<br> protocol C;<br><br> handlers {<br> pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";<br> pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";<br> local-io-error "echo o > /proc/sysrq-trigger ; halt -f";<br> outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";<br> before-resync-target /usr/local/bin/resync-start-RAID6.sh;<br> after-resync-target /usr/local/bin/resync-end-RAID6.sh;<br> split-brain "/usrlib/drbd/notify-split-brain.sh root";<br> }<br><br> startup {<br> degr-wfc-timeout 120;<br> }<br><br> disk {<br> on-io-error detach;<br> }<br><br> net {<br> cram-hmac-alg sha1;<br> shared-secret "password";<br> after-sb-0pri discard-zero-changes;<br> after-sb-1pri discard-secondary;<br> after-sb-2pri disconnect;<br> rr-conflict disconnect;<br> sndbuf-size 0;<br> max-buffers 8000;<br> max-epoch-size 8000;<br> }<br><br> syncer {<br> rate 30M;<br> verify-alg sha1;<br># al-extents 257;<br> al-extents 3389;<br> }<br><br> on iscsi-filer-1 {<br> device /dev/drbd0;<br> disk /dev/md0;<br> address 192.168.10.1:7789;<br> flexible-meta-disk internal;<br> }<br><br> on iscsi-filer-2 {<br> device /dev/drbd0;<br> disk /dev/md0;<br> address 192.168.10.2:7789;<br> flexible-meta-disk internal;<br> }<br>}<br><br><br>resource iscsi.target.1 {<br> protocol C;<br><br> handlers {<br> pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";<br> pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";<br> local-io-error "echo o > /proc/sysrq-trigger ; halt -f";<br> outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";<br> before-resync-target /usr/local/bin/resync-start-RAID1.sh;<br> after-resync-target /usr/local/bin/resync-end-RAID1.sh;<br> split-brain "/usrlib/drbd/notify-split-brain.sh root";<br> }<br><br> startup {<br> degr-wfc-timeout 120;<br> }<br><br> disk {<br> on-io-error detach;<br> }<br><br> net {<br> cram-hmac-alg sha1;<br> shared-secret "password";<br> after-sb-0pri discard-zero-changes;<br> after-sb-1pri discard-secondary;<br> after-sb-2pri disconnect;<br> rr-conflict disconnect;<br> sndbuf-size 0;<br> max-buffers 8000;<br> max-epoch-size 8000;<br> }<br><br> syncer {<br> rate 30M;<br> verify-alg sha1;<br># al-extents 257;<br> al-extents 3389;<br> }<br><br> on iscsi-filer-1 {<br> device /dev/drbd1;<br> disk /dev/md1;<br> address 192.168.10.1:7790;<br> flexible-meta-disk internal;<br> }<br><br> on iscsi-filer-2 {<br> device /dev/drbd1;<br> disk /dev/md1;<br> address 192.168.10.2:7790;<br> flexible-meta-disk internal;<br> }<br>}<br><br><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Cesar Peschiera" <brain@click.com.py><br><b>To: </b>"Gerald Brandt" <gbr@majentis.com><br><b>Sent: </b>Wednesday, June 26, 2013 10:24:52 PM<br><b>Subject: </b>Re: [DRBD-user] r0 ok, r1 PingAck did not arrive in time<br><br>
<style></style>
<div><font face="Arial" size="2"><strong>Please Gerald, answer this
question:</strong></font></div>
<div><font face="Arial" size="2">What are the model and brand of your NICs for use
with DRBD on each PVE Node?</font></div>
<div><font face="Arial" size="2">If you don't know, you can remove the NIC of the
mainboard and see in the chipset that said</font></div>
<div><font face="Arial"><font size="2"><font face="Arial" size="2"></font></font></font> </div>
<div><font face="Arial" size="2"><strong>And suggestions:</strong></font></div>
<div><span id="result_box" class="short_text" lang="en"><span class="hps">Please</span>
<span class="hps">follow the steps</span> <span class="hps">in this
order:</span></span></div>
<div><font face="Arial"><font size="2"><span class="short_text" lang="en"><span class="hps">1- If you have configured "HA" for the VMs with Virtual disks on the
DRBD resource , disable "HA" for these VMs.</span></span></font></font></div>
<div><font face="Arial"><font size="2"><span class="short_text" lang="en"><span class="hps">2- Power off your VMs that have his virtual disks on the DRBD
resource</span></span></font></font></div>
<div><font face="Arial"><font size="2"><span class="short_text" lang="en"><span class="hps">
<div><font face="Arial"><font size="2">3- Make backup of all your VMs that have his
virtual disks on the DRBD resource (<span id="result_box" class="short_text" lang="en"><span class="hps">just as a
precaution)</span></span></font></font></div></span></span></font></font></div>
<div><font face="Arial"><font size="2"><span class="short_text" lang="en"><span class="hps">4- Run on each PVE Node<strong>:</strong> "<strong>service drbd stop
&& chkconfig drbd off</strong>"</span></span></font></font></div>
<div><font face="Arial" size="2">5- Run on each PVE node<strong>:</strong>
"<strong>aptitude update && aptitude full-upgrade</strong>"</font></div>
<div><font face="Arial" size="2">6- Reboot the PVE Nodes with have the DRBD
resources</font></div>
<div><font face="Arial" size="2">7- Run on each PVE Node<strong>:</strong>
<strong>aptitude install pve-headers-`uname -r`</strong> #<span id="result_box" class="short_text" lang="en"><font size="3"><font face="Times New Roman"><span class="hps">do not forget</span> <span class="hps alt-edited">the punctuation
marks</span></font></font></span></font></div>
<div><font face="Arial" size="2">7- With this you will have the latest PVE version
in your system, and his new kernel need DRBD 8.3.13, so you must be compile
and install it</font></div>
<div><font face="Arial" size="2"> (I think that you know how
do it)</font></div>
<div><font face="Arial" size="2">8- Configure the new directives of DRBD if this is
necessary</font></div>
<div><font face="Arial" size="2">
<div><font face="Arial"><font size="2"><span class="short_text" lang="en"><span class="hps">9- Run on all Nodes with have the DRBD
service<strong>:</strong></span></span></font></font></div>
<div><font face="Arial"><font size="2"><span class="short_text" lang="en"><span class="hps"><strong>cp /var/log/kern.log /var/log/kern.log.bak && cat
/dev/null
>/var/log/kern.log</strong></span></span></font></font></div></font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">10- Run on each PVE Node: "<strong>service drbd
start && chkconfig drbd on</strong>" (with this, the DRBD resources will
make updates in the other PVE Node), and wait until that DRBD resource has been
updated ( for this, you can run for see the progress with this
command<strong>:</strong> <strong>watch cat /proc/drbd</strong> )</font></div>
<div><font face="Arial" size="2">11- When the DRBD resources has been updated, If
"HA" was enabled, now you can enable it.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">After of follow this steps, shows the result of:
"<strong>cat /var/log/kern.log</strong>" and "<strong>cat
/proc/drbd</strong>"</font></div>
<div><font face="Arial"><font size="2"><font face="Arial" size="2"></font></font></font> </div>
<div><font face="Arial" size="2">Best regards</font></div>
<div><font face="Arial" size="2">Cesar</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">----- Original Message ----- </font>
<div><font face="Arial" size="2">From: "Gerald Brandt" <</font><a href="mailto:gbr@majentis.com" target="_blank"><font face="Arial" size="2">gbr@majentis.com</font></a><font face="Arial" size="2">></font></div>
<div><font face="Arial" size="2">To: "cesar" <</font><a href="mailto:brain@click.com.py" target="_blank"><font face="Arial" size="2">brain@click.com.py</font></a><font face="Arial" size="2">></font></div>
<div><font face="Arial" size="2">Cc: <</font><a href="mailto:drbd-user@lists.linbit.com" target="_blank"><font face="Arial" size="2">drbd-user@lists.linbit.com</font></a><font face="Arial" size="2">></font></div>
<div><font face="Arial" size="2">Sent: Wednesday, June 26, 2013 10:12
PM</font></div>
<div><font face="Arial" size="2">Subject: Re: [DRBD-user] r0 ok, r1 PingAck did not
arrive in time</font></div></div>
<div><font face="Arial"><br><font size="2"></font></font></div><font face="Arial" size="2">> Hi,<br>> <br>> I'm running Intel e1000 with crossover
cable, and I just noticed in my log files I'm getting this:<br>> <br>>
[3535162.766591] e1000e: eth1 NIC Link is Down<br>> [3535168.243278] e1000e:
eth1 NIC Link is Up 10 Mbps Full Duplex, Flow Control: Rx/Tx<br>>
[3535168.243282] e1000e 0000:02:00.0: eth1: 10/100 speed: disabling TSO<br>>
[3535176.574432] e1000e: eth1 NIC Link is Down<br>> [3535178.495165] e1000e:
eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx<br>>
[3535214.602022] e1000e: eth1 NIC Link is Down<br>> [3535214.602465] e1000e
0000:02:00.0: eth1: Reset adapter<br>> [3535239.602540] e1000e: eth1 NIC Link
is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx<br>> <br>>
Interesting. <br>> <br>> Gerald<br>> <br>> <br>> -----
Original Message -----<br>>> From: "cesar" <</font><a href="mailto:brain@click.com.py" target="_blank"><font face="Arial" size="2">brain@click.com.py</font></a><font face="Arial" size="2">><br>>>
To: </font><a href="mailto:drbd-user@lists.linbit.com" target="_blank"><font face="Arial" size="2">drbd-user@lists.linbit.com</font></a><br><font face="Arial" size="2">>> Sent: Wednesday, June 26, 2013 5:56:17 PM<br>>>
Subject: Re: [DRBD-user] r0 ok, r1 PingAck did not arrive in time<br>>>
<br>>> Hi Lukas Gradl-4<br>>> <br>>> I have PVE 2.3 with
the same problem<br>>> <br>>> But my NICs are Realtek, and soon i
will change of brand for Intel,<br>>> and i<br>>> have connected in
crossover-cable mode, because a "Switch" in the<br>>> middle
can<br>>> change the data of the packets.<br>>> <br>>> Please
answer this questions:<br>>> <br>>> What are the model of your NICs
for use with DRBD on each PVE Node?<br>>> <br>>> Do you have the
link in crossover-cable mode (ie link NIC to NIC)?,<br>>> if
not,<br>>> just do it !!! (DRBD suggested highly do NIC to
NIC)<br>>> <br>>> The latest "PVE 2.3" and "PVE 3.x" version have
the kernel for<br>>> support DRBD<br>>> 8.3.13, update your PVE and
your DRBD and after you must do test.<br>>> After,<br>>>
please tell me about of this test.<br>>> <br>>> When i have my
new NICs Intel, i will can tell you about of my<br>>>
experiences<br>>> <br>>> Best regards<br>>> Cesar<br>>>
<br>>> <br>>> <br>>> --<br>>> View this message in
context:<br>>> </font><a href="http://drbd.10923.n7.nabble.com/r0-ok-r1-PingAck-did-not-arrive-in-time-tp17953p17960.html" target="_blank"><font face="Arial" size="2">http://drbd.10923.n7.nabble.com/r0-ok-r1-PingAck-did-not-arrive-in-time-tp17953p17960.html</font></a><br><font face="Arial" size="2">>> Sent from the DRBD - User mailing list archive at
Nabble.com.<br>>>
_______________________________________________<br>>> drbd-user mailing
list<br>>> </font><a href="mailto:drbd-user@lists.linbit.com" target="_blank"><font face="Arial" size="2">drbd-user@lists.linbit.com</font></a><br><font face="Arial" size="2">>> </font><a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank"><font face="Arial" size="2">http://lists.linbit.com/mailman/listinfo/drbd-user</font></a><br><font face="Arial" size="2">>> <br>></font> </blockquote><br></div></body></html>