<div>Oh hai! Chimmin' in late! Reply in-line:</div><div><br></div>On Tue, Mar 8, 2011 at 9:23 AM, Dennis Jacobfeuerborn <span dir="ltr"><<a href="mailto:dennisml@conversis.de">dennisml@conversis.de</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">[root@storage2 ~]# fdisk -l /dev/drbd1<br>
<br>
Disk /dev/drbd1: 1073 MB, 1073672192 bytes<br>
255 heads, 63 sectors/track, 130 cylinders<br>
Units = cylinders of 16065 * 512 = 8225280 bytes<br>
<br>
Device Boot Start End Blocks Id System<br>
/dev/drbd1p1 1 25 200781 83 Linux<br>
/dev/drbd1p2 26 50 200812+ 83 Linux<br>
<br>
[root@storage2 ~]# ls -d /dev/drbd*<br>
/dev/drbd /dev/drbd0 /dev/drbd1<br>
<br>
I've already rebooted both nodes but the device nodes never show up in /dev. Is there anything special that needs to be done for this to happen?</blockquote><div><br></div><div>Same thing that needs to happen anytime you hot-add LUNs and want to detect their partitions: run 'partprobe' It's an order of operations thing, the initscripts get all the partition, then use those partitions to setup DRBD devices, which in turn have more partitions you need to detect but the initscripts assume all the partitions are discovered by the time DRBD starts so it never checks again. Invoking 'partprobe' manually invokes partition discovery. This is rather distribution specific initialization detail, but that's the deal.</div>
<div><br></div><div>-JR</div></div>