<div>Hi Felix,</div>
<div> </div>
<div>Thaks for the info and sorry for the late response I had a week off for the holidays. When I try to manually establish the connection between the nodes, not via heartbeat, I get the following state:</div>
<div> </div>
<div># modprobe drbd</div>
<div>[root@cpvmdc1 conf.d]# drbdadm up r0</div>
<div>[root@cpvmdc1 conf.d]# drbdadm primary r0<br>[root@cpvmdc1 conf.d]# cat /proc/drbd<br>version: 8.4.0 (api:1/proto:86-100)<br>GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by <a href="mailto:root@cpvmdc1">root@cpvmdc1</a>, 2011-12-21 17:13:05<br>
0: cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown C r----s<br> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:200736</div>
<div> </div>
<div> </div>
<div>Now, I can see the node listening on port 7788:</div>
<div> </div>
<div>[root@cpvmdc1 private]# netstat -tuplen | grep 7788<br>tcp 0 0 <a href="http://192.168.1.100:7788">192.168.1.100:7788</a> 0.0.0.0:* LISTEN 0 290311 -</div>
<div> </div>
<div> </div>
<div>On the secondary:</div>
<div> </div>
<div>[root@cpvmdc2 ~]# modprobe drbd<br>[root@cpvmdc2 ~]# drbdadm up r0<br>[root@cpvmdc2 ~]# cat /proc/drbd<br>version: 8.4.0 (api:1/proto:86-100)<br>GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by <a href="mailto:root@cpvmdc1">root@cpvmdc1</a>, 2011-12-21 17:13:05<br>
0: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----s<br> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:200736</div>
<div>[root@cpvmdc2 ~]# drbdadm connect r0<br>[root@cpvmdc2 ~]# cat /proc/drbd<br>version: 8.4.0 (api:1/proto:86-100)<br>GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by <a href="mailto:root@cpvmdc1">root@cpvmdc1</a>, 2011-12-21 17:13:05<br>
0: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----s<br> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:200736</div>
<div> </div>
<div>but after the "connect" command on the secondary node, the node stays in StandAlone and I can't see port 7788 open on it. Also the connection state of the primary changes from WFConnection to StandAlone:</div>
<div> </div>
<div>[root@cpvmdc1 conf.d]# cat /proc/drbd<br>version: 8.4.0 (api:1/proto:86-100)<br>GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by <a href="mailto:root@cpvmdc1">root@cpvmdc1</a>, 2011-12-21 17:13:05<br> 0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----s<br>
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:200736</div>
<div> </div>
<div>and it gives up trying to connect.</div>
<div> </div>
<div><br>My drbd resource config file looks like this now:</div>
<div> </div>
<div>[root@cpvmdc1 conf.d]# cat /etc/drbd.d/r0.res <br>resource r0 {<br> meta-disk internal;<br> device minor 0;<br> net {<br> protocol C;<br> }<br> disk { on-io-error detach; }<br>
syncer {<br> rate 100M;<br> verify-alg md5;<br> }<br> on cpvmdc1 {<br> device /dev/drbd0;<br> address <a href="http://192.168.1.100:7788">192.168.1.100:7788</a>;<br>
disk /dev/sdc1;<br> meta-disk internal;<br> }<br> on cpvmdc2 {<br> device /dev/drbd0;<br> address <a href="http://192.168.1.101:7788">192.168.1.101:7788</a>;<br>
disk /dev/sdc1;<br> meta-disk internal;<br> }<br>}</div>
<div> </div>
<div> </div>
<div>When I run the "syncer" option for drbdadm I get:</div>
<div> </div>
<div>[root@cpvmdc1 conf.d]# drbdadm syncer r0<br>drbdadm: Unknown command 'syncer'</div>
<div> </div>
<div>Am I still missing somethinfg?</div>
<div> </div>
<div>Thanks again for your help<br><br>Igor</div>
<div> </div>
<div class="gmail_quote">On Fri, Dec 23, 2011 at 7:27 PM, Felix Frank <span dir="ltr"><<a href="mailto:ff@mpexnet.de">ff@mpexnet.de</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi,<br>
<div class="im"><br>On 12/23/2011 03:37 AM, Igor Cicimov wrote:<br>> Thanks to both of you guys for your help. Now the error is gone but they<br>> are still in StandAlone mode instead of connected:<br><br></div>did you start DRBD by initscript? Looks as though you used "drbdadm<br>
attach" on each node. Don't do that.<br>You should use "drbdadm up" to activate a resource.<br><br>Now that the disks are already attached, you can just do<br>"drbdadm syncer" then "drbdadm connect", on each node respectively.<br>
<div class="im"><br>> It's also strange<br>> that I'm sure I formated drbd partition with ext3 but is showing as ext2<br>> in mount:<br><br></div>Ext3 is downwards compatible. You can mount ext3 partitions as ext2, and<br>
your kernel will refrain from using the ext3 journal.<br><br>Is there an fstab entry for drbd0? Does it specify ext2 as filesystem?<br>Or did you mount that manually?<br><br>Either way, just be sure that mount knows the FS is supposed to have a<br>
journal, and this should Just Work.<br><br>HTH,<br>Felix<br></blockquote></div><br>