<HTML dir=ltr><HEAD><TITLE>Re: [DRBD-user] drbd consistently crashes during WFConnect</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16608" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText13432 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Thanks to Florian, who pointed out the typo in our config file!</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>All us db guys looking at this frequently call this software drdb, and type it that way at times. An unfortunate coincidence (for us at least).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>It's too bad that drbd crashes on this instead of politely pointing out (like Florian did), that device /dev/drdb0 does not exist. I would say that is a bug.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>THANKS AGAIN FLORIAN! It's working now.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Alex</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> drbd-user-bounces@lists.linbit.com on behalf of Lars Ellenberg<BR><B>Sent:</B> Wed 3/5/2008 2:50 AM<BR><B>To:</B> drbd-user@lists.linbit.com<BR><B>Subject:</B> Re: [DRBD-user] drbd consistently crashes during WFConnect<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>On Tue, Mar 04, 2008 at 02:02:16PM -0600, Langley, Alex wrote:<BR>> Setup:<BR>><BR>> Both servers HP DL380 G3, Fedora Core 6, Kernel 2.6.22<BR>><BR>> /etc/drbd.conf<BR>><BR>> global {<BR>> usage-count no;<BR>> }<BR>><BR>> common {<BR>> syncer { rate 1M; }<BR>> }<BR>><BR>> resource drive2 {<BR>> protocol C;<BR>> startup {<BR>> wfc-timeout 60;<BR>> degr-wfc-timeout 60;<BR>> }<BR>> disk {<BR>> on-io-error detach;<BR>> }<BR>> net {<BR>> max-buffers 2048;<BR>> ko-count 4;<BR>> after-sb-0pri disconnect;<BR>> rr-conflict disconnect;<BR>> # #cram-hmac-alg sha1;<BR>> # #shared-secret "WorldWarIFlyingAce";<BR>> }<BR>> on wamperf1 { #PRIMARY<BR>> device /dev/drdb0;<BR>> disk /dev/cciss/c0d0p5;<BR>> address 10.12.138.57:7791;<BR>> meta-disk /dev/cciss/c0d0p6[0];<BR>> }<BR>> on wamperf2 { #SECONDARY<BR>> device /dev/drbd0;<BR>> disk /dev/cciss/c0d0p5;<BR>> address 10.12.138.62:7791;<BR>> meta-disk /dev/cciss/c0d0p6[0];<BR>> }<BR>> }<BR>> The following shows up on the console of the primary a few seconds after<BR>> bringing drbd up and making it primary<BR>><BR>> drbd: no version for "struct_module" found: kernel tainted.<BR>> drbd0: No usable activity log found.<BR>> drbd0: Barriers not supported on meta data device - disabling<BR>> BUG: unable to handle kernel NULL pointer dereference at virtual address<BR>> 00000032<BR>> printing eip:<BR>> c062e172<BR>> *pde = 3d5a1067<BR>> Oops: 0002 [#1]<BR>> SMP<BR>> last sysfs file: /block/drbd0/range<BR>> Modules linked in: drbd(F)(U) ipv6 autofs4 sunrpc dm_mirror dm_mod video<BR><BR>I dare say you forced a module into your kernel that was not built for<BR>this particular kernel. don't do that, or bad things will happen.<BR><BR>go, start over, build again, this time hopefully one matching your kernel.<BR><BR>--<BR>: Lars Ellenberg <A href="http://www.linbit.com/">http://www.linbit.com</A> :<BR>: DRBD/HA support and consulting sales at linbit.com :<BR>: LINBIT Information Technologies GmbH Tel +43-1-8178292-0 :<BR>: Vivenotgasse 48, A-1120 Vienna/Europe Fax +43-1-8178292-82 :<BR>__<BR>please use the "List-Reply" function of your email client.<BR>_______________________________________________<BR>drbd-user mailing list<BR>drbd-user@lists.linbit.com<BR><A href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</A><BR></FONT></P></DIV>
<BR>
______________________________________________________________________<BR>
This message contains information which may be confidential and/or privileged. Unless you are the intended recipient (or authorized to receive for the intended recipient), you may not read, use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message and any attachment(s) thereto without retaining any copies.<BR>
______________________________________________________________________<BR>
</BODY></HTML>