Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Fri, Jun 5, 2009 at 2:24 PM, Sam Howard
<sam.howard at officepcsupport.com> wrote:
> 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?
I am having a similar problem on drbd 8.3.7. Two machines have been
running happily for several weeks. One has 17 drbd resources, the
other has 18. When I try to add a new resource on either machine
drbdsetup fails but there is nothing reported in syslog, messages,
dmesg, etc.
host2:/etc/drbd.d# drbdsetup 34 disk /dev/vg/video /dev/vg/video
internal --set-defaults --create-device
34: Failure: (127) Device minor not allocated
Where can I find meaningful information regarding the failure?
Keith Coleman