OpenVZ Forum


Home » Mailing lists » Users » OpenVz + DRBD
OpenVz + DRBD [message #15175] Fri, 20 July 2007 12:23 Go to next message
Jorge Cabello is currently offline  Jorge Cabello
Messages: 2
Registered: July 2007
Junior Member
From: openvz.org
Hi,

Im trying to use DRBD inside an OpenVz Virtual Node but I can't access
the kernel module from inside the node.

I tried to follow wiki howto (HA cluster with DRBD and Heartbeat) but
when I start drbd inside the node I get the next error:

stone101# /etc/init.d/drbd start
Starting DRBD resources: No response from the DRBD driver! Is the
module loaded?
[ d0 No response from the DRBD driver! Is the module loaded?
State change failed: (0)unknown error.

cmd /sbin/drbdsetup /dev/drbd0 disk /dev/sda7 /dev/sda7 flexible
--set-defaults --create-device --on-io-error=detach failed!


The kernel module is installed in the kernel as lsmod shows (result at
the end of the email). Im using a kernel 2.6.20 with OpenVz patch:
patch-ovz007.1-combined.gz

Im probably missing something, as I'm just starting to use these tools,
but I can't find what it is.

Does someone know what it could be?

Thanks
Jorge


These are the results of some commands:
Inside Hardware Node
-----------------------
stone# lsmod
Module Size Used by
drbd 194372 0
simfs 5348 1
vzdquota 40148 1 [permanent]
firmware_class 9984 0
vznetdev 16960 3
vzethdev 11656 0
vzmon 33032 3 vznetdev,vzethdev
vzdev 3588 6 vzdquota,vznetdev,vzethdev,vzmon


Inside Virtual Node
------------
stone101# lsmod
Module Size Used by


stone101# cat /proc/drbd
version: 8.0.0 (api:86/proto:86)
SVN Revision: 2713 build by root@dhcp0-176.sw.ru, 2007-03-05 16:06:51
0: cs:Unconfigured


DRBD Tools were compiled from source code. First entry of ChangeLog
file:
8.0.0 (api:86/proto:86)
--------
* No effecitve changes to rc2.
Re: OpenVz + DRBD [message #15207 is a reply to message #15175] Sat, 21 July 2007 10:42 Go to previous messageGo to next message
Daniel Pittman is currently offline  Daniel Pittman
Messages: 26
Registered: January 2007
Junior Member
From: openvz.org
Jorge Cabello <jorge@aspl.es> writes:

> Im trying to use DRBD inside an OpenVz Virtual Node but I can't access
> the kernel module from inside the node.

[...]

> Im probably missing something, as I'm just starting to use these
> tools, but I can't find what it is.

You didn't mention using the vzctl tool to grant read/write permissions
to the DRBD device anywhere in your notes. See the manual page for the
'devnodes' or 'devices' arguments.

Regards,
Daniel
--
Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707 email: contact@digital-infrastructure.com.au
http://digital-infrastructure.com.au/
Re: OpenVz + DRBD [message #21875 is a reply to message #15207] Wed, 17 October 2007 11:31 Go to previous message
Jorge Cabello is currently offline  Jorge Cabello
Messages: 2
Registered: July 2007
Junior Member
From: openvz.org
Hi, 

Sorry for the delay in the answer but I have been working in other
proyects.

I granted permissions to the virtual node using:
 HN# vzctl set 202 --devices b:147:0:rw

If I dont load manually the kernel module in the hardware node when I
start drbd in the virtual node I get the following:

  Starting DRBD resources:    Can not load the drbd module.

But if I start the kernel module manually before starting drbd there is
a kernel Ooops (kernel log in attachment) and the virtual node reports:

  Starting DRBD resources:    No response from the DRBD driver! Is the
module loaded?
  Error code 10943 unknown.
  You should updated the drbd userland tools.

With the same tools version (8.0.6) drbd works properly inside hardware
node.

Anyone has been able to run drbd inside a virtual node?


El sáb, 21-07-2007 a las 20:42 +1000, Daniel Pittman escribió:
> Jorge Cabello <jorge@aspl.es> writes:
> 
> > Im trying to use DRBD inside an OpenVz Virtual Node but I can't access
> > the kernel module from inside the node.
> 
> [...]
> 
> > Im probably missing something, as I'm just starting to use these
> > tools, but I can't find what it is.
> 
> You didn't mention using the vzctl tool to grant read/write permissions
> to the DRBD device anywhere in your notes.  See the manual page for the
> 'devnodes' or 'devices' arguments.
> 
> Regards,
>         Daniel

stone kernel: CR2: 0000000000000016
Oct 17 13:13:56 stone kernel: Unable to handle kernel NULL pointer dereference at 0000000000000016 RIP: 
Oct 17 13:13:56 stone kernel:  [<ffffffff88026eed>] :drbd:drbd_nl_disk_conf+0x1dd/0x760
Oct 17 13:13:56 stone kernel: PGD 32789067 PUD 30abb067 PMD 0 
Oct 17 13:13:56 stone kernel: Oops: 0000 [1] 
Oct 17 13:13:56 stone kernel: CPU: 0 
Oct 17 13:13:56 stone kernel: Modules linked in: drbd simfs vznetdev vzethdev vzdquota vzmon vzdev bridge llc forcedeth
Oct 17 13:13:56 stone kernel: Pid: 161, comm: cqueue/0 Not tainted 2.6.20-ovz007 #2
Oct 17 13:13:56 stone kernel: RIP: 0060:[<ffffffff88026eed>]  [<ffffffff88026eed>] :drbd:drbd_nl_disk_conf+0x1dd/0x760
Oct 17 13:13:56 stone kernel: RSP: 0068:ffff810037c05d90  EFLAGS: 00010282
Oct 17 13:13:56 stone kernel: RAX: fffffffffffffffe RBX: ffff810036be4000 RCX: 0000000000000282
Oct 17 13:13:56 stone kernel: RDX: fffffffffffffffe RSI: ffffffff80281f00 RDI: ffff810030f96080
Oct 17 13:13:56 stone kernel: RBP: 0000000000000068 R08: 0000000000000001 R09: 0000000000000000
Oct 17 13:13:56 stone kernel: R10: 0000000000000000 R11: 00000000000000aa R12: ffff8100316abe24
Oct 17 13:13:56 stone kernel: R13: ffff8100379459c0 R14: ffff8100379459c0 R15: ffff8100354edb54
Oct 17 13:13:56 stone kernel: FS:  00002abf425ab6d0(0000) GS:ffffffff80597000(0000) knlGS:0000000000000000
Oct 17 13:13:56 stone kernel: CS:  0060 DS: 0018 ES: 0018 CR0: 000000008005003b
Oct 17 13:13:56 stone kernel: CR2: 0000000000000016 CR3: 0000000030533000 CR4: 00000000000006e0
Oct 17 13:13:56 stone kernel: Process cqueue/0 (pid: 161, veid=0, threadinfo ffff810037c04000, task ffff810037e55000)
Oct 17 13:13:56 stone kernel: Stack:  0000000000000000 0000000000000000 ffff8100316abe24 0000000000000030
Oct 17 13:13:56 stone kernel:  ffff8100354edb40 ffff8100316abe24 ffff8100316abe10 ffff810036be4000
Oct 17 13:13:56 stone kernel:  ffffffff8803e010 ffffffff880286cd ffff810037c05e60 ffff810031bca568
Oct 17 13:13:56 stone kernel: Call Trace:
Oct 17 13:13:56 stone kernel:  [<ffffffff880286cd>] :drbd:drbd_connector_callback+0xfd/0x1a0
Oct 17 13:13:56 stone kernel:  [<ffffffff80385ddc>] cn_queue_wrapper+0x1c/0x50
Oct 17 13:13:56 stone kernel:  [<ffffffff80385dc0>] cn_queue_wrapper+0x0/0x50
Oct 17 13:13:56 stone kernel:  [<ffffffff8023d504>] run_workqueue+0x94/0x130
Oct 17 13:13:56 stone kernel:  [<ffffffff8023d6f8>] worker_thread+0x158/0x1a0
Oct 17 13:13:56 stone kernel:  [<ffffffff80225e10>] default_wake_function+0x0/0x10
Oct 17 13:13:56 stone kernel:  [<ffffffff80225e10>] default_wake_function+0x0/0x10
Oct 17 13:13:56 stone kernel:  [<ffffffff8023d5a0>] worker_thread+0x0/0x1a0
Oct 17 13:13:56 stone kernel:  [<ffffffff8023d5a0>] worker_thread+0x0/0x1a0
Oct 17 13:13:56 stone kernel:  [<ffffffff802413ff>] kthread+0x8f/0xd0
Oct 17 13:13:56 stone kernel:  [<ffffffff8020a428>] child_rip+0xa/0x12
Oct 17 13:13:56 stone kernel:  [<ffffffff80241370>] kthread+0x0/0xd0
Oct 17 13:13:56 stone kernel:  [<ffffffff8020a41e>] child_rip+0x0/0x12
Oct 17 13:13:56 stone kernel: 
Oct 17 13:13:56 stone kernel: 
Oct 17 13:13:56 stone kernel: Code: 48 8b 40 18 bd 6b 00 00 00 4c 8b 60 08 41 0f b7 84 24 b2 00 
Oct 17 13:13:56 stone kernel: RIP  [<ffffffff88026eed>] :drbd:drbd_nl_disk_conf+0x1dd/0x760
Oct 17 13:13:56 stone kernel:  RSP <ffff810037c05d90>
Oct 17 13:13:56 stone kernel: CR2: 0000000000000016
  • Attachment: oops.txt
    (Size: 3.29KB, Downloaded 263 times)
Previous Topic: boot error - unable to mount root fs on unknown-block(0,0)
Next Topic: Unable to start VPS on Debian Etch
Goto Forum:
  


Current Time: Wed Nov 14 08:35:12 GMT 2018