Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DRBD: Users

Kernel oops on create-md

 

 

DRBD users RSS feed   Index | Next | Previous | View Threaded


stef at aoc-uk

Oct 15, 2009, 6:10 AM

Post #1 of 4 (816 views)
Permalink
Kernel oops on create-md

Hello,

I'm attempting to run drbd 8.3.4 against Linux 2.31.4. I'm making the
(possibly incorrect) assumption that from the Changelog,

8.3.3
* Following Linux upstream changes 2.6.31

that I'm ok on the 2.6.31 kernel series.

I've patched the kernel directly and can see from

root [ /sources/drbd-8.3.4 ]# cat /proc/drbd
version: 8.3.4 (api:88/proto:86-91)
GIT-hash: 70a645ae080411c87b4482a135847d69dc90a6a2 build by
root [at] atuin-, 2009-10-15 11:36:31

that the patch has been applied correctly.

My problem is that when I attempt to create the metadata I get a kernel
Oops, output of which is attached. I've also included my drbd.conf, very
basic, but there you have it.

Problem is 100% reproduceable both on this machine and it's (identical)
counterpart which will (eventually) form the second node in the cluster.

I've wondered if it is a kernel compatibility problem,

I've also wonder if drbd doesn't like to run on a software mirror (md
device), though am guided by "You can stack DRBD on top of md, md on top
of DRBD is nonsense, however." from
http://www.linux-ha.org/DataRedundancyByDrbd. Further discussion on this
list from a couple of years ago is quite confusing!

I wonder if anyone can provide some advice?

Kind regards

Stef
--
Stefan Morrell | Operations Director
Tel: 0845 3452820 | Alpha Omega Computers Ltd
Fax: 0845 3452830 | Incorporating Level 5 Internet
stef [at] aoc-uk | stef [at] l5net

Standard Disclaimer: http://www.aoc-uk.com/16.asp

Alpha Omega Computers Ltd, Batley Technology Centre, Grange Road,
Batley, WF17 6ER.
Registered in England No. 3867142. VAT No. GB734421454
Attachments: oops.txt (1.43 KB)
  drbd.conf (0.36 KB)


lars.ellenberg at linbit

Oct 15, 2009, 6:24 AM

Post #2 of 4 (756 views)
Permalink
Re: Kernel oops on create-md [In reply to]

On Thu, Oct 15, 2009 at 02:10:54PM +0100, Stef Morrell wrote:
> Hello,
>
> I'm attempting to run drbd 8.3.4 against Linux 2.31.4. I'm making the
> (possibly incorrect) assumption that from the Changelog,
>
> 8.3.3
> * Following Linux upstream changes 2.6.31
>
> that I'm ok on the 2.6.31 kernel series.
>
> I've patched the kernel directly and can see from
>
> root [ /sources/drbd-8.3.4 ]# cat /proc/drbd
> version: 8.3.4 (api:88/proto:86-91)
> GIT-hash: 70a645ae080411c87b4482a135847d69dc90a6a2 build by
> root [at] atuin-, 2009-10-15 11:36:31
>
> that the patch has been applied correctly.

Nope.

> My problem is that when I attempt to create the metadata I get a kernel
> Oops, output of which is attached. I've also included my drbd.conf, very
> basic, but there you have it.
>
> Problem is 100% reproduceable both on this machine and it's (identical)
> counterpart which will (eventually) form the second node in the cluster.
>
> I've wondered if it is a kernel compatibility problem,

Yes.

> I wonder if anyone can provide some advice?

You patched it wrong. Sorry.

If you get any compile warnings during the module build,
you got it wrong again. So try again.

--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


stef at aoc-uk

Oct 15, 2009, 7:17 AM

Post #3 of 4 (750 views)
Permalink
Re: Kernel oops on create-md [In reply to]

Hello,

> -----Original Message-----
> From: drbd-user-bounces [at] lists
> [mailto:drbd-user-bounces [at] lists] On Behalf Of Lars
> Ellenberg
> Sent: 15 October 2009 14:25
> To: drbd-user [at] lists
> Subject: Re: [DRBD-user] Kernel oops on create-md
>
> On Thu, Oct 15, 2009 at 02:10:54PM +0100, Stef Morrell wrote:
> > Hello,
> >
> > I'm attempting to run drbd 8.3.4 against Linux 2.31.4. I'm
> making the
> > (possibly incorrect) assumption that from the Changelog,
> >
> > 8.3.3
> > * Following Linux upstream changes 2.6.31
> >
> > that I'm ok on the 2.6.31 kernel series.
> >
> > I've patched the kernel directly and can see from
> >
> > root [ /sources/drbd-8.3.4 ]# cat /proc/drbd
> > version: 8.3.4 (api:88/proto:86-91)
> > GIT-hash: 70a645ae080411c87b4482a135847d69dc90a6a2 build by
> > root [at] atuin-, 2009-10-15 11:36:31
> >
> > that the patch has been applied correctly.
>
> Nope.
>
> > My problem is that when I attempt to create the metadata I get a
> > kernel Oops, output of which is attached. I've also included my
> > drbd.conf, very basic, but there you have it.
> >
> > Problem is 100% reproduceable both on this machine and it's
> > (identical) counterpart which will (eventually) form the
> second node in the cluster.
> >
> > I've wondered if it is a kernel compatibility problem,
>
> Yes.
>
> > I wonder if anyone can provide some advice?
>
> You patched it wrong. Sorry.

Do you mean that 2.6.31.4 isn't supported at all, or that I've made a
mistake in the patching process itself? (Log of patching process
attached). If it is the kernel version, what is actually the latest
which drbd supports?

> If you get any compile warnings during the module build, you
> got it wrong again. So try again.

Yes. One compile warning - does seem to fit with the oops.

gcc -Wp,-MD,drivers/block/drbd/.drbd_nl.o.d -nostdinc -isystem
/usr/lib/gcc/i686-pc-linux-gnu/4.4.1/include -Iinclude
-I/sources/linux-2.6.31.4/arch/x86/include -include
include/linux/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes
-Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -Wno-format-security
-fno-delete-null-pointer-checks -O2 -m32 -msoft-float -mregparm=3
-freg-struct-return -mpreferred-stack-boundary=2 -march=i686
-mtune=pentium4 -Wa,-mtune=generic32 -ffreestanding -fstack-protector
-fstack-protector-all -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
-pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse
-mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=2048
-fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign
-fno-strict-overflow -fno-dwarf2-cfi-asm -DMODULE -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(drbd_nl)"
-D"KBUILD_MODNAME=KBUILD_STR(drbd)" -c -o drivers/block/drbd/drbd_nl.o
drivers/block/drbd/drbd_nl.c
drivers/block/drbd/drbd_nl.c: In function 'drbd_nl_init':
drivers/block/drbd/drbd_nl.c:2380: warning: passing argument 3 of
'cn_add_callback' from incompatible pointer type
include/linux/connector.h:170: note: expected 'void (*)(void *)' but
argument is of type 'void (*)(struct cn_msg *, struct netlink_skb_parms
*)'

Regards

Stef
Attachments: buildlog.txt (2.83 KB)


lars.ellenberg at linbit

Oct 15, 2009, 8:25 AM

Post #4 of 4 (749 views)
Permalink
Re: Kernel oops on create-md [In reply to]

On Thu, Oct 15, 2009 at 03:17:40PM +0100, Stef Morrell wrote:
> Hello,
>
> > -----Original Message-----
> > From: drbd-user-bounces [at] lists
> > [mailto:drbd-user-bounces [at] lists] On Behalf Of Lars
> > Ellenberg
> > Sent: 15 October 2009 14:25
> > To: drbd-user [at] lists
> > Subject: Re: [DRBD-user] Kernel oops on create-md
> >
> > On Thu, Oct 15, 2009 at 02:10:54PM +0100, Stef Morrell wrote:
> > > Hello,
> > >
> > > I'm attempting to run drbd 8.3.4 against Linux 2.31.4. I'm
> > making the
> > > (possibly incorrect) assumption that from the Changelog,
> > >
> > > 8.3.3
> > > * Following Linux upstream changes 2.6.31
> > >
> > > that I'm ok on the 2.6.31 kernel series.
> > >
> > > I've patched the kernel directly and can see from
> > >
> > > root [ /sources/drbd-8.3.4 ]# cat /proc/drbd
> > > version: 8.3.4 (api:88/proto:86-91)
> > > GIT-hash: 70a645ae080411c87b4482a135847d69dc90a6a2 build by
> > > root [at] atuin-, 2009-10-15 11:36:31
> > >
> > > that the patch has been applied correctly.
> >
> > Nope.
> >
> > > My problem is that when I attempt to create the metadata I get a
> > > kernel Oops, output of which is attached. I've also included my
> > > drbd.conf, very basic, but there you have it.
> > >
> > > Problem is 100% reproduceable both on this machine and it's
> > > (identical) counterpart which will (eventually) form the
> > second node in the cluster.
> > >
> > > I've wondered if it is a kernel compatibility problem,
> >
> > Yes.
> >
> > > I wonder if anyone can provide some advice?
> >
> > You patched it wrong. Sorry.
>
> Do you mean that 2.6.31.4 isn't supported at all, or that I've made a
> mistake in the patching process itself? (Log of patching process
> attached). If it is the kernel version, what is actually the latest
> which drbd supports?

I mean you patched it wrong.

> > If you get any compile warnings during the module build, you
> > got it wrong again. So try again.
>
> Yes. One compile warning - does seem to fit with the oops.
>
> drivers/block/drbd/drbd_nl.c: In function 'drbd_nl_init':
> drivers/block/drbd/drbd_nl.c:2380: warning: passing argument 3 of
> 'cn_add_callback' from incompatible pointer type

yep.

> root [ /sources/drbd-8.3.4 ]# make KDIR=/sources/linux-2.6.31.4 kernel-patch

forget about that.
_that_ is not supported.
sometimes it works, sometime it does not.
if it does not work, it does not work.

it may help if you do a "normal" out-of-tree module build, before you
generate the patch. there is some automatic adjustment of compatibility
ifdefs going on.

if it does not help,
don't use the "kernel-patch" approach.

--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

DRBD users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.