Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
i am running drbd version Version: 8.0.11 (api:86) on two ubuntu hardy
servers.
drbd ist running on top of lvm with internal metadata.
Kernel is: 2.6.24-19-xen
Till now i got no problems with drbd. I got over 40 resources up and
running.
Today i wanted to add resources 44 and 45.
so what i made was the following (each on both nodes, via cluster ssh,
so i made the exact same things):
- created the lvm disks via lvcreate
- created the internal metadata
- added the new resources to the drbd.conf
- performed an /etc/init.d/drbd reload
that worked on one host, but not on the other.
It told me:
root at xen3:~# /etc/init.d/drbd reload
* Reloading DRBD configuration
Failure: (127) Device minor not allocated
Command '/sbin/drbdsetup /dev/drbd44 disk /dev/data1/vsrv-www2-disk
/dev/data1/vsrv-www2-disk internal --set-defaults --create-device'
terminated with exit code 10
so wheres the problem?
root at xen3:~# ls -l /dev/drbd44
brw-rw---- 1 root disk 147, 44 2009-03-09 09:26 /dev/drbd44
root at xen3:~# ls -l /dev/drbd45
brw-rw---- 1 root disk 147, 45 2009-03-09 09:27 /dev/drbd45
the devices were created and did not exists before (i tried to add
resource 46 and 47 as well to test this. same result).
my drbd.conf looks like this:
#
# global
#
global {
usage-count no;
}
#
# common
#
common {
protocol C;
syncer { rate 33M; }
}
...
#
# vsrv-www2
#
resource vsrv-www2-disk {
net {}
startup {
wfc-timeout 5;
}
on xen3 {
device /dev/drbd44;
disk /dev/data1/vsrv-www2-disk;
address 192.168.1.3:7834;
meta-disk internal;
}
on xen4 {
device /dev/drbd44;
disk /dev/data1/vsrv-www2-disk;
address 192.168.1.4:7834;
meta-disk internal;
}
}
resource vsrv-www2-swap {
net {}
startup {
wfc-timeout 5;
}
on xen3 {
device /dev/drbd45;
disk /dev/data1/vsrv-www2-swap;
address 192.168.1.3:7835;
meta-disk internal;
}
on xen4 {
device /dev/drbd45;
disk /dev/data1/vsrv-www2-swap;
address 192.168.1.4:7835;
meta-disk internal;
}
}
in dmesg i found:
[12574226.859838] sysfs: duplicate filename 'drbd44' can not be created
[12574226.859851] WARNING: at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/fs/sysfs/dir.c:424
sysfs_add_one()
[12574226.859854] Pid: 6569, comm: cqueue/2 Not tainted 2.6.24-19-xen #1
[12574226.859855]
[12574226.859856] Call Trace:
[12574226.859877] [<ffffffff802efe68>] sysfs_add_one+0xb8/0xf0
[12574226.859880] [<ffffffff802f0480>] create_dir+0x60/0xb0
[12574226.859884] [<ffffffff802f0501>] sysfs_create_dir+0x31/0x50
[12574226.859887] [<ffffffff80336d12>] kobject_get+0x12/0x20
[12574226.859890] [<ffffffff80337333>] kobject_add+0xb3/0x200
[12574226.859893] [<ffffffff802e9a76>] register_disk+0x56/0x240
[12574226.859897] [<ffffffff8032da14>] add_disk+0x34/0x40
[12574226.859908] [<ffffffff88322d7e>] :drbd:drbd_new_device+0xde/0x1e0
[12574226.859912] [<ffffffff883020f0>] :cn:cn_queue_wrapper+0x0/0x30
[12574226.859920] [<ffffffff88324c7d>] :drbd:ensure_mdev+0x4d/0x110
[12574226.859926] [<ffffffff88326373>]
:drbd:drbd_connector_callback+0x53/0x1f0
[12574226.859930] [<ffffffff883020f0>] :cn:cn_queue_wrapper+0x0/0x30
[12574226.859933] [<ffffffff883020ff>] :cn:cn_queue_wrapper+0xf/0x30
[12574226.859937] [<ffffffff80248202>] run_workqueue+0xb2/0x190
[12574226.859941] [<ffffffff80248e40>] worker_thread+0x0/0x110
[12574226.859943] [<ffffffff80248ee3>] worker_thread+0xa3/0x110
[12574226.859946] [<ffffffff8024cc20>] autoremove_wake_function+0x0/0x30
[12574226.859950] [<ffffffff80248e40>] worker_thread+0x0/0x110
[12574226.859952] [<ffffffff80248e40>] worker_thread+0x0/0x110
[12574226.859954] [<ffffffff8024c83b>] kthread+0x4b/0x80
[12574226.859957] [<ffffffff8020d018>] child_rip+0xa/0x12
[12574226.859961] [<ffffffff8024c7f0>] kthread+0x0/0x80
[12574226.859963] [<ffffffff8020d00e>] child_rip+0x0/0x12
[12574226.859965]
[12574226.859968] kobject_add failed for drbd44 with -EEXIST, don't try
to register things with the same name in the same directory.
[12574226.860070] Pid: 6569, comm: cqueue/2 Not tainted 2.6.24-19-xen #1
[12574226.860071]
[12574226.860071] Call Trace:
[12574226.860074] [<ffffffff803373c9>] kobject_add+0x149/0x200
[12574226.860077] [<ffffffff802e9a76>] register_disk+0x56/0x240
[12574226.860080] [<ffffffff8032da14>] add_disk+0x34/0x40
[12574226.860087] [<ffffffff88322d7e>] :drbd:drbd_new_device+0xde/0x1e0
[12574226.860093] [<ffffffff883020f0>] :cn:cn_queue_wrapper+0x0/0x30
[12574226.860100] [<ffffffff88324c7d>] :drbd:ensure_mdev+0x4d/0x110
[12574226.860106] [<ffffffff88326373>]
:drbd:drbd_connector_callback+0x53/0x1f0
[12574226.860111] [<ffffffff883020f0>] :cn:cn_queue_wrapper+0x0/0x30
[12574226.860114] [<ffffffff883020ff>] :cn:cn_queue_wrapper+0xf/0x30
[12574226.860116] [<ffffffff80248202>] run_workqueue+0xb2/0x190
[12574226.860120] [<ffffffff80248e40>] worker_thread+0x0/0x110
[12574226.860122] [<ffffffff80248ee3>] worker_thread+0xa3/0x110
[12574226.860124] [<ffffffff8024cc20>] autoremove_wake_function+0x0/0x30
[12574226.860130] [<ffffffff80248e40>] worker_thread+0x0/0x110
[12574226.860133] [<ffffffff80248e40>] worker_thread+0x0/0x110
[12574226.860134] [<ffffffff8024c83b>] kthread+0x4b/0x80
[12574226.860136] [<ffffffff8020d018>] child_rip+0xa/0x12
[12574226.860146] [<ffffffff8024c7f0>] kthread+0x0/0x80
[12574226.860148] [<ffffffff8020d00e>] child_rip+0x0/0x12
can anyone help me out?
regards
Sebastian