Mailing List Archive

Well I already solved it - had to uninstall the kernel-ovs, download the
kernel-ovs-2.6.18-8.1.15.3.1.el5, because apparently drbd is only
compatible with that kernel, then install the kernel-ovs-devel for that
version, then build and install the modules...
and now I can't build it on my other server because it won't let me
install glibc, because I changed to the earlier kernel too soon...

And I already fixed the typo in my drbd.conf....


Chris


From: Wood.Chris@tatravelcenters.com
To: drbd-user@lists.linbit.com
Date: 03/18/2010 03:11 PM
Subject: [DRBD-user] DRBD module won't load
Sent by: drbd-user-bounces@lists.linbit.com



Hello

I'm trying to start drbd on an Oracle Virtual Server (Xen) machine. I get
this error:

Starting DRBD resources: Can not load the drbd module.

I have these packages installed

$ rpm -qa|grep drbd
drbd-pacemaker-8.3.6-1.el5
drbd-bash-completion-8.3.6-1.el5
drbd-8.3.6-1.el5
kmod-drbd-8.0.16-5.el5_3
drbd-utils-8.3.6-1.el5
drbd-xen-8.3.6-1.el5
drbd-heartbeat-8.3.6-1.el5

/etc/drbd.conf
global {
usage-count no;
}
common {
protocol C;
}
resource r0 {
disk {
fencing resouce-only;
}
handlers {
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
}
syncer {
rate 40M;
}
on admin-lab-ovs0 {
device /dev/drbd0;
disk /dev/sda3;
address 10.98.4.90:7789;
meta-disk internal;
}
on admin-lab-ovs1 {
device /dev/drbd0;
disk /dev/sda3;
address 10.98.4.91:7789;
meta-disk internal;
}
}

My kernel is Linux 2.6.18-128.2.1.4.9.el5xen #1 SMP Fri Oct 9 14:57:31 EDT

2009

Here are the messages from the log

Mar 17 13:06:09 admin-lab-ovs0 modprobe: FATAL: Module drbd not found.
Mar 17 13:08:44 admin-lab-ovs0 modprobe: FATAL: Module drbd not found.
Mar 17 13:18:02 admin-lab-ovs0 yum: Installed:
kmod-drbd-8.0.16-5.el5_3.i686
Mar 17 13:20:27 admin-lab-ovs0 modprobe: FATAL: Module drbd not found.
Mar 17 13:21:12 admin-lab-ovs0 kernel: drbd: disagrees about version of
symbol struct_module
Mar 18 04:42:24 admin-lab-ovs0 modprobe: FATAL: Module drbd not found.

Any help would be much appreciated - do I have to build the module from
scratch?

Thanks,
Chris
_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user

From: Wood.Chris@tatravelcenters.com
> I'm trying to start drbd on an Oracle Virtual Server (Xen) machine.
> Starting DRBD resources: Can not load the drbd module.
> $ rpm -qa|grep drbd
> drbd-8.3.6-1.el5
> kmod-drbd-8.0.16-5.el5_3

drbd 8.3.6, drbd kernel module 8.0.16. The two really should match, no?
And which /lib/modules/2.6.* dir did the module get installed in? If it
got put in the wrong dir (possible) then modprobe won't find it. Where
did the kernel module RPM come from? It has to be built against the
kernel that's running, otherwise it won't work.

> Any help would be much appreciated - do I have to build the module from
> scratch?

Building the kernel module from source should be pretty easy; just go
into the drbd source dir and do "make rpm KDIR=/usr/src/kernels/2.6.18-blah"
and you should get RPMs for userland and kernelspace drbd components.
Not applicable to very recent kernels since drbd is now in the vanilla
kernel source, but CentOS 5 doesn't have a recent kernel.

--
Matt G / Dances With Crows
The Crow202 Blog: http://crow202.org/wordpress/
There is no Darkness in Eternity/But only Light too dim for us to see


_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user

Matt, thanks for your reply.

I did go change my kernel and I was able to compile and install the drbd
module on server0 - now I can't on server1, even though it's running the
exact same kernel, because it won't install the right version of gcc.

I tried yum install kmod-drbd and that's what it gave me. yum doesn't seem
to care if the versions match.

So I did a make rpm...
You have now:
-rw-r--r-- 1 root root 212405 Mar 18 11:11
dist/RPMS/i386/drbd-8.3.4-3.i386.rpm
-rw-r--r-- 1 root root 1012695 Mar 18 11:11
dist/RPMS/i386/drbd-km-2.6.18_8.1.15.3.1.el5xen-8.3.4-3.i386.rpm

Looks nice, but I have drbd-8.3.6 installed... oops. So I downloaded the
source for drbd-8.3.6

Well wouldn't ya know it

make module does not work
make rpm does not work

/usr/bin/rpmbuild -tb \
--define "kernelversion " \
--define "kdir /usr/src/linux" \
\
drbd-8.3.6.tar.gz
error: Macro %kernelversion has empty body
error: Macro %kernelversion has empty body
error: Macro %kernelversion has empty body
error: Name field must be present in package: (main package)
error: Version field must be present in package: (main package)
error: Release field must be present in package: (main package)
error: Summary field must be present in package: (main package)
error: Group field must be present in package: (main package)
error: License field must be present in package: (main package)
make: *** [rpm] Error 1

So now what? The rpm build seems to only work with 8.3.4...

I noticed in the 8.3.6 Makefile, module: and rpm: are prefaced by .PHONY:
.. so how do I get around this?

Or can I just install the
drbd-km-2.6.18_8.1.15.3.1.el5xen-8.3.4-3.i386.rpm on both machines and be
done with it?

Thanks for your help

Chris


From: "Matt Graham" <danceswithcrows@usa.net>
To: <drbd-user@lists.linbit.com>
Date: 03/18/2010 03:33 PM
Subject: Re: [DRBD-user] DRBD module won't load
Sent by: drbd-user-bounces@lists.linbit.com



From: Wood.Chris@tatravelcenters.com
> I'm trying to start drbd on an Oracle Virtual Server (Xen) machine.
> Starting DRBD resources: Can not load the drbd module.
> $ rpm -qa|grep drbd
> drbd-8.3.6-1.el5
> kmod-drbd-8.0.16-5.el5_3

drbd 8.3.6, drbd kernel module 8.0.16. The two really should match, no?
And which /lib/modules/2.6.* dir did the module get installed in? If it
got put in the wrong dir (possible) then modprobe won't find it. Where
did the kernel module RPM come from? It has to be built against the
kernel that's running, otherwise it won't work.

> Any help would be much appreciated - do I have to build the module from
> scratch?

Building the kernel module from source should be pretty easy; just go
into the drbd source dir and do "make rpm
KDIR=/usr/src/kernels/2.6.18-blah"
and you should get RPMs for userland and kernelspace drbd components.
Not applicable to very recent kernels since drbd is now in the vanilla
kernel source, but CentOS 5 doesn't have a recent kernel.

--
Matt G / Dances With Crows
The Crow202 Blog: http://crow202.org/wordpress/
There is no Darkness in Eternity/But only Light too dim for us to see


_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user

drbd-user-bounces@lists.linbit.com wrote on 03/18/2010 03:27:10 PM:

> From: "Matt Graham" <danceswithcrows@usa.net>
> To: <drbd-user@lists.linbit.com>
> Date: 03/18/2010 03:33 PM
> Subject: Re: [DRBD-user] DRBD module won't load
> Sent by: drbd-user-bounces@lists.linbit.com
>
> From: Wood.Chris@tatravelcenters.com
> > I'm trying to start drbd on an Oracle Virtual Server (Xen) machine.
> > Starting DRBD resources: Can not load the drbd module.
> > $ rpm -qa|grep drbd
> > drbd-8.3.6-1.el5
> > kmod-drbd-8.0.16-5.el5_3
>
> drbd 8.3.6, drbd kernel module 8.0.16. The two really should match, no?
> And which /lib/modules/2.6.* dir did the module get installed in? If it
> got put in the wrong dir (possible) then modprobe won't find it. Where
> did the kernel module RPM come from? It has to be built against the
> kernel that's running, otherwise it won't work.
>
> > Any help would be much appreciated - do I have to build the module
from
> > scratch?
>
> Building the kernel module from source should be pretty easy; just go
> into the drbd source dir and do "make rpm
KDIR=/usr/src/kernels/2.6.18-blah"
> and you should get RPMs for userland and kernelspace drbd components.
> Not applicable to very recent kernels since drbd is now in the vanilla
> kernel source, but CentOS 5 doesn't have a recent kernel.

Ok, I uninstalled all the other packages... so I have no idea if I'll be
able to get this to work with heartbeat and openais... but I built the
8.3.4 versions and installed on both hosts.

I set up dedicated interfaces on each, they are directly connected. I
opened the firewall for that interface. I can ping each server from the
other over this link, although the xenbr1 interface is bridging it - I
don't really want that, but can't find anything on how to disable xen from
grabbing it... so I can ping each server, but when I start drbd on each
node, it just waits and waits and waits for the other node to come up...

Here's what I see in the log on server0

Mar 18 13:08:52 admin-lab-ovs0 kernel: drbd: initialized. Version: 8.3.4
(api:88/proto:86-91)
Mar 18 13:08:52 admin-lab-ovs0 kernel: drbd: GIT-hash:
70a645ae080411c87b4482a135847d69dc90a6a2 build by root@admin-lab-ovs0,
2010-03-18 11:28:37
Mar 18 13:08:52 admin-lab-ovs0 kernel: drbd: registered as block device
major 147
Mar 18 13:08:52 admin-lab-ovs0 kernel: drbd: minor_table @ 0xdf50c0c0
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: Starting worker thread
(from cqueue/0 [120])
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: disk( Diskless ->
Attaching )
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: No usable activity log
found.
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: Method to ensure write
ordering: barrier
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: max_segment_size ( =
BIO size ) = 32768
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: drbd_bm_resize called
with capacity == 1942729272
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: resync bitmap:
bits=242841159 words=7588788
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: size = 926 GB
(971364636 KB)
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: recounting of set bits
took additional 15 jiffies
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: 926 GB (242841159
bits) marked out-of-sync by on disk bit-map.
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: disk( Attaching ->
Inconsistent )
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: conn( StandAlone ->
Unconnected )
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: Starting receiver
thread (from drbd0_worker [2871])
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: receiver (re)started
Mar 18 13:08:52 admin-lab-ovs0 kernel: block drbd0: conn( Unconnected ->
WFConnection )
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: Handshake successful:
Agreed network protocol version 91
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: conn( WFConnection ->
WFReportParams )
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: Starting asender
thread (from drbd0_receiver [2881])
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: data-integrity-alg:
<not-used>
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: drbd_sync_handshake:
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: self
0000000000000004:0000000000000000:0000000000000000:0000000000000000
bits:242841159 flags:0
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: peer
0000000000000004:0000000000000000:0000000000000000:0000000000000000
bits:242841159 flags:0
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: uuid_compare()=0 by
rule 10
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: No resync, but
242841159 bits in bitmap!
Mar 18 13:09:51 admin-lab-ovs0 kernel: block drbd0: peer( Unknown ->
Secondary ) conn( WFReportParams -> Connected ) pdsk( DUnknown ->
Inconsistent )
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: peer( Secondary ->
Unknown ) conn( Connected -> Disconnecting )
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: short read expecting
header on sock: r=-512
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: asender terminated
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: Terminating asender
thread
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: Connection closed
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: conn( Disconnecting ->
StandAlone )
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: receiver terminated
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: Terminating receiver
thread
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: conn( StandAlone ->
Unconnected )
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: Starting receiver
thread (from drbd0_worker [2871])
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: receiver (re)started
Mar 18 13:28:42 admin-lab-ovs0 kernel: block drbd0: conn( Unconnected ->
WFConnection )

[root@admin-lab-ovs0 cwood]# cat /proc/drbd
version: 8.3.4 (api:88/proto:86-91)
GIT-hash: 70a645ae080411c87b4482a135847d69dc90a6a2 build by
root@admin-lab-ovs0, 2010-03-18 11:28:37
0: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/Inconsistent C
r----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
oos:971364636


And server1

Mar 18 18:03:47 admin-lab-ovs1 kernel: drbd: initialized. Version: 8.3.4
(api:88/proto:86-91)
Mar 18 18:03:47 admin-lab-ovs1 kernel: drbd: GIT-hash:
70a645ae080411c87b4482a135847d69dc90a6a2 build by root@admin-lab-ovs0,
2010-03-18 11:28:37
Mar 18 18:03:47 admin-lab-ovs1 kernel: drbd: registered as block device
major 147
Mar 18 18:03:47 admin-lab-ovs1 kernel: drbd: minor_table @ 0xf718b6c0
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: Starting worker thread
(from cqueue/0 [120])
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: disk( Diskless ->
Attaching )
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: No usable activity log
found.
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: Method to ensure write
ordering: barrier
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: max_segment_size ( =
BIO size ) = 32768
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: drbd_bm_resize called
with capacity == 1942729272
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: resync bitmap:
bits=242841159 words=7588788
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: size = 926 GB
(971364636 KB)
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: recounting of set bits
took additional 18 jiffies
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: 926 GB (242841159
bits) marked out-of-sync by on disk bit-map.
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: disk( Attaching ->
Inconsistent )
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: conn( StandAlone ->
Unconnected )
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: Starting receiver
thread (from drbd0_worker [3206])
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: receiver (re)started
Mar 18 18:03:47 admin-lab-ovs1 kernel: block drbd0: conn( Unconnected ->
WFConnection )
Mar 18 18:04:06 admin-lab-ovs1 kernel: block drbd0: Handshake successful:
Agreed network protocol version 91
Mar 18 18:04:06 admin-lab-ovs1 kernel: block drbd0: conn( WFConnection ->
WFReportParams )
Mar 18 18:04:06 admin-lab-ovs1 kernel: block drbd0: Starting asender
thread (from drbd0_receiver [3216])
Mar 18 18:04:06 admin-lab-ovs1 kernel: block drbd0: data-integrity-alg:
<not-used>
Mar 18 18:04:07 admin-lab-ovs1 kernel: block drbd0: drbd_sync_handshake:
Mar 18 18:04:07 admin-lab-ovs1 kernel: block drbd0: self
0000000000000004:0000000000000000:0000000000000000:0000000000000000
bits:242841159 flags:0
Mar 18 18:04:07 admin-lab-ovs1 kernel: block drbd0: peer
0000000000000004:0000000000000000:0000000000000000:0000000000000000
bits:242841159 flags:0
Mar 18 18:04:07 admin-lab-ovs1 kernel: block drbd0: uuid_compare()=0 by
rule 10
Mar 18 18:04:07 admin-lab-ovs1 kernel: block drbd0: No resync, but
242841159 bits in bitmap!
Mar 18 18:04:07 admin-lab-ovs1 kernel: block drbd0: peer( Unknown ->
Secondary ) conn( WFReportParams -> Connected ) pdsk( DUnknown ->
Inconsistent )
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: peer( Secondary ->
Unknown ) conn( Connected -> TearDown )
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: asender terminated
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: Terminating asender
thread
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: Connection closed
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: conn( TearDown ->
Unconnected )
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: receiver terminated
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: Restarting receiver
thread
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: receiver (re)started
Mar 18 18:22:58 admin-lab-ovs1 kernel: block drbd0: conn( Unconnected ->
WFConnection )

[root@admin-lab-ovs1 cwood]# cat /proc/drbd
version: 8.3.4 (api:88/proto:86-91)
GIT-hash: 70a645ae080411c87b4482a135847d69dc90a6a2 build by
root@admin-lab-ovs0, 2010-03-18 11:28:37
0: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/Inconsistent C
r----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
oos:971364636
_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user