Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I have a similar setup (ubuntu 8.04 hosts, xen guests of various flavors). I created 2 new LVs on each host, updated and pushed the drbd.conf (snippet): resource pd01-root { device /dev/drbd32; disk /dev/datavg/pd01-root; meta-disk /dev/datavg/drbd_log[32]; on xen-80-31-00 { address 192.168.250.14:7732; } on xen-33-18-02 { address 192.168.250.12:7732; } } ====== "drbdadm create-md pd01-root" works on both hosts, "drbdadm up pd01-root" and "drbdadm -- -o primary pd01-root" works on one of the nodes, but the other node cannot "up" or even "connect" to the new device. ====== root at xen-80-31-00:~# drbdsetup 32 net 192.168.250.14:7732 192.168.250.12:7732 C --set-defaults --create-device --allow-two-primaries 32: Failure: (127) Device minor not allocated ====== no messages in /var/log or dmesg to give a hint. "drbdadm status" shows: <!-- resource minor="32" name="pd01-root" not available or not yet created --> which is expected. I've done the start/stop drbd, reboot, etc. This is on DRBD 8.3.1, Xen 3.4.0, linux 2.6.18.8 (with XenSource patches) -- same build on both hosts. What can I try next to get more information for debugging this? Thanks, Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090605/b0477ea8/attachment.htm>