Just a bit more info ... found this in my dmesg:<div><br></div><div><div>kobject_add failed for drbd102 with -EEXIST, don't try to register things with the same name in the same directory.</div><div><br></div><div>Call Trace:</div>
<div> [<ffffffff802e6727>] kobject_add+0x174/0x19f</div><div> [<ffffffff802dde50>] exact_lock+0x0/0x14</div><div> [<ffffffff80340b22>] cn_queue_wrapper+0x0/0x23</div><div> [<ffffffff802b9406>] register_disk+0x43/0x199</div>
<div> [<ffffffff80340b22>] cn_queue_wrapper+0x0/0x23</div><div> [<ffffffff802ddfd9>] add_disk+0x34/0x3d</div><div> [<ffffffff882605c6>] :drbd:drbd_new_device+0xd5/0x1fc</div><div> [<ffffffff8826297d>] :drbd:ensure_mdev+0x3b/0xde</div>
<div> [<ffffffff88265676>] :drbd:drbd_connector_callback+0x41/0x1d9</div><div> [<ffffffff80340b22>] cn_queue_wrapper+0x0/0x23</div><div> [<ffffffff80340b2d>] cn_queue_wrapper+0xb/0x23</div><div> [<ffffffff8023e53b>] run_workqueue+0x94/0xfe</div>
<div> [<ffffffff80241a4d>] keventd_create_kthread+0x0/0x61</div><div> [<ffffffff8023f0c3>] worker_thread+0x104/0x13d</div><div> [<ffffffff80227086>] default_wake_function+0x0/0xe</div><div> [<ffffffff8023efbf>] worker_thread+0x0/0x13d</div>
<div> [<ffffffff80241cc3>] kthread+0xd4/0x109</div><div> [<ffffffff8020afb8>] child_rip+0xa/0x12</div><div> [<ffffffff80241a4d>] keventd_create_kthread+0x0/0x61</div><div> [<ffffffff80241bef>] kthread+0x0/0x109</div>
<div> [<ffffffff8020afae>] child_rip+0x0/0x12</div><div><br></div><br><div class="gmail_quote">On Mon, Feb 2, 2009 at 12:00 AM, Sam Howard <span dir="ltr"><<a href="mailto:sam.howard@officepcsupport.com">sam.howard@officepcsupport.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi.<div><br></div><div>I'm still struggling to get a stacked device to work on DRBD 8.3.0.</div><div><br></div><div>
Config excerpt:</div><div><br></div><div><div>common {</div><div> syncer {</div><div> rate 70M;</div>
<div> verify-alg md5;<br></div><div> }<br></div><div><br></div><div> protocol C;</div><div><br></div><div> startup {</div><div> wfc-timeout 0; ## Infinite!</div><div> degr-wfc-timeout 120; ## 2 minutes.</div>
<div> }</div><div><br></div><div> disk {</div><div> on-io-error detach;</div><div> }</div><div><br></div><div> net {</div><div> allow-two-primaries;<br></div><div> }</div><div>}</div><div><br></div><div><div>resource ftp01-root {</div>
<div> device /dev/drbd2;</div><div> disk /dev/datavg/ftp01-root;</div><div> flexible-meta-disk internal;</div><div><br></div><div> on xen-33-18-02 {</div><div> address <a href="http://192.168.250.12:7702" target="_blank">192.168.250.12:7702</a>;</div>
<div> }</div><div><br></div><div> on xen-33-18-03 {</div><div> address <a href="http://192.168.250.13:7702" target="_blank">192.168.250.13:7702</a>;</div><div> }</div><div>} # ftp01-root</div><div><br></div><div>
resource ftp01-root-b {</div>
<div> device /dev/drbd2;</div><div> disk /dev/datavg/ftp01-root;</div><div> meta-disk /dev/datavg/drbd_log[2];</div><div><br></div><div> on xen-80-31-00 {</div><div> address <a href="http://192.168.250.14:7702" target="_blank">192.168.250.14:7702</a>;</div>
<div> }</div><div><br></div><div> on xen-80-31-01 {</div><div> address <a href="http://192.168.250.15:7702" target="_blank">192.168.250.15:7702</a>;</div><div> }</div><div>} # ftp01-root-b</div><div><br></div><div>
resource ftp01-root-r {</div>
<div> protocol A;</div><div><br></div><div> stacked-on-top-of ftp01-root {</div><div> device /dev/drbd102;</div><div> address <a href="http://10.80.31.51:7702" target="_blank">10.80.31.51:7702</a>;</div>
<div> }</div>
<div><div><br></div><div> stacked-on-top-of ftp01-root-b {</div><div> device /dev/drbd102;</div><div> address <a href="http://10.80.31.50:7702" target="_blank">10.80.31.50:7702</a>;</div><div> }</div><div>
} # ftp01-root-r</div>
<div><br></div><div>=========================================</div><div><br></div><div>I have the ftp01-root device up and running (currently in use and working fine). I build my new server (xen-80-31-00) and got its device "ftp01-root-b" running.</div>
<div><br></div><div>xen-33-18-03 (ftp01-root):</div><div><div> 2: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r---</div><div> ns:2176532 nr:999236 dw:3190465 dr:2068626 al:79 bm:78 lo:0 pe:0 ua:0 ap:0 e</div>
<div>p:1 wo:b oos:1420</div><div><br></div><div>xen-80-31-00 (ftp01-root-b):</div><div><div> 2: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r---</div><div> 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:4194304</div>
<div><br></div><div>On both hosts, the other node is down, hence the "DUnknown" for the second host.</div><div><br></div><div>Trying to create the stacked device fails with:</div><div><br></div></div><div><div>
root@xen-33-18-03:/etc# drbdadm --stacked up ftp01-root-r</div>
<div>/dev/drbd102: Failure: (127) Device minor not allocated</div><div>Command 'drbdsetup /dev/drbd102 disk /dev/drbd2 /dev/drbd2 internal --set-defaults --create-device --on-io-error=detach' terminated with exit code 10</div>
<div><br></div><div>I do see the device (/dev/drbd102) *is* getting created:</div><div><br></div><div><div>brw-rw---- 1 root disk 147, 102 2009-02-02 01:37 /dev/drbd102</div><div><br></div></div></div></div><div>Google has not been much help, and I'm really stuck now.</div>
<div><br></div><div>Just to make it more fun, it seems the batch of Samsung 750GB drives that are in the xen-33-18-xx servers aren't very good and I'm loosing drives left and right, so I need to get this data moved ASAP.</div>
<div><br></div><div>What can I try next?</div><div><br></div><div>Thanks,</div><div>Sam</div></div></div></div>
</blockquote></div><br></div>