Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Florian Haas wrote:
> Andre,
>
> known issue. Configure a valid cram-hmac-alg and use a shared secret.
> Will be fixed in 8.2.1.
>
Hi Florian,
thanks for fast response
I changed my drbd.conf
net { timeout 60; connect-int 10; ping-int 10;
max-buffers 2048; max-epoch-size 2048;
cram-hmac-alg sha1; shared-secret "blah";
rebootet the server and nevertheless I got a kernel oops
Andre
> Note: since this error occurs on disconnect, you'll need to force a reboot
> after updating your drbd.conf.
>
> Cheers,
> Florian
>
> On Monday 29 October 2007 11:13:38 Andre Konopka wrote:
>> Hi,
>>
>> as the previous version, drbd doesn't compile out of the box on
>> SLES9.(kzmalloc problem)
>>
>> I inserted the KZALLOC stuff from wrappers in cn_queue.c (as Lars
>> recommended for 8.0.6)
>>
>> #ifdef NEED_BACKPORT_OF_KZALLOC
>>
>> static inline void *kzalloc(size_t size, int flags)
>> {
>> void *rv = kmalloc(size,flags);
>> if(rv) memset(rv,0,size);
>>
>> return rv;
>> }
>>
>> #endif
>>
>> and then it compiles perfectly.
>>
>>
>>
>> Here comes my drbd.conf
>>
>> global {
>> usage-count no;
>> }
>> common {
>> syncer { rate 50M; }
>> }
>> resource a1 {
>> protocol C;
>> startup { wfc-timeout 0; degr-wfc-timeout 120; }
>> disk { on-io-error detach; }
>> net { timeout 60; connect-int 10; ping-int 10;
>> max-buffers 2048; max-epoch-size 2048; }
>> on pdxrs001 {
>> device /dev/drbd0;
>> disk /dev/vgadc/lvol1;
>> address 149.221.248.27:7790;
>> flexible-meta-disk /dev/vgadc/drbdmeta-lvol1;
>> }
>> on pdxrs002 {
>> device /dev/drbd0;
>> disk /dev/vgadc/lvol1;
>> address 149.221.248.29:7790;
>> flexible-meta-disk /dev/vgadc/drbdmeta-lvol1;
>> }
>> }
>>
>>
>> I did the following steps to initialize my drbd disk...
>>
>> lvcreate -L 5G -n lvol1 /dev/vgadc
>> lvcreate -L 4M -n drbdmeta-lvol1 vgadc
>>
>> modprobe drbd
>> drbdadm create-md a1
>> drbdadm up a1
>>
>> drbdadm state a1
>> Secondary/Unknown
>>
>>
>> After entering
>>
>> drbadm down a1
>>
>> I saw the following oops in the logfile
>>
>> Oct 29 12:25:24 pdxrs001 kernel: drbd0: No usable activity log found.
>> Oct 29 12:25:24 pdxrs001 kernel: drbd1: No usable activity log found.
>> Oct 29 12:25:39 pdxrs001 kernel: drbd0: Discarding network configuration.
>> Oct 29 12:25:39 pdxrs001 kernel: drbd0: tl_clear()
>> Oct 29 12:25:39 pdxrs001 kernel: Unable to handle kernel NULL pointer
>> dereference at 0000000000000000 RIP:
>> Oct 29 12:25:39 pdxrs001 kernel:
>> <ffffffffa0232877>{:drbd:drbd_disconnect+1335}
>> Oct 29 12:25:39 pdxrs001 kernel: PML4 39fa6067 PGD 38352067 PMD 0
>> Oct 29 12:25:39 pdxrs001 kernel: Oops: 0000 [1] SMP
>> Oct 29 12:25:39 pdxrs001 kernel: CPU 0
>> Oct 29 12:25:39 pdxrs001 kernel: Pid: 7404, comm: drbd0_receiver
>> Tainted: G U (2.6.5-7.244-smp )
>> Oct 29 12:25:39 pdxrs001 kernel: RIP: 0010:[<ffffffffa0232877>]
>> <ffffffffa0232877>{:drbd:drbd_disconnect+1335}
>> Oct 29 12:25:39 pdxrs001 kernel: RSP: 0018:0000010034393e38 EFLAGS:
>> 00010212
>> Oct 29 12:25:39 pdxrs001 kernel: RAX: 0000000000000010 RBX:
>> 0000000000000000 RCX: 000001000000c000
>> Oct 29 12:25:39 pdxrs001 kernel: RDX: 0000000000197a71 RSI:
>> 000000000000774c RDI: 000001003fe52080
>> Oct 29 12:25:39 pdxrs001 kernel: RBP: 000001003516e800 R08:
>> 0000000000000036 R09: 0000000000000000
>> Oct 29 12:25:39 pdxrs001 kernel: R10: 00000000ffffffff R11:
>> 0000000000000000 R12: 000000000000c812
>> Oct 29 12:25:39 pdxrs001 kernel: R13: 000001003516eb30 R14:
>> 000001003516ed28 R15: 000001003516ecf8
>> Oct 29 12:25:39 pdxrs001 kernel: FS: 0000000000000000(0000)
>> GS:ffffffff8057cb80(0000) knlGS:0000000000000000
>> Oct 29 12:25:39 pdxrs001 kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
>> 000000008005003b
>> Oct 29 12:25:39 pdxrs001 kernel: CR2: 0000000000000000 CR3:
>> 0000000000101000 CR4: 00000000000006e0
>> Oct 29 12:25:39 pdxrs001 kernel: Process drbd0_receiver (pid: 7404,
>> threadinfo 0000010034392000, task 00000100390ca3e0)
>> Oct 29 12:25:39 pdxrs001 kernel: Stack: 0000010034393e48
>> 000001003516ed08 0000000000000000 0000000000000206
>> Oct 29 12:25:39 pdxrs001 kernel: 0000000000000000
>> 00000100390ca3e0 ffffffff8013d3e0 0000010034393ea0
>> Oct 29 12:25:39 pdxrs001 kernel: 0000010034393ea0 000001003b34b6d0
>> Oct 29 12:25:39 pdxrs001 kernel: Call
>> Trace:<ffffffff8013d3e0>{autoremove_wake_function+0}
>> <ffffffff8013d3e0>{autoremove_wake_function+0}
>> Oct 29 12:25:39 pdxrs001 kernel:
>> <ffffffffa022b950>{:drbd:w_prev_work_done+0}
>> <ffffffffa0232aa8>{:drbd:drbdd_init+232}
>> Oct 29 12:25:39 pdxrs001 kernel:
>> <ffffffffa023f0f7>{:drbd:drbd_thread_setup+151}
>> <ffffffff801111b7>{child_rip+8}
>> Oct 29 12:25:39 pdxrs001 kernel:
>> <ffffffffa023f060>{:drbd:drbd_thread_setup+0}
>> <ffffffff801111af>{child_rip+0}
>> Oct 29 12:25:39 pdxrs001 kernel:
>> Oct 29 12:25:39 pdxrs001 kernel:
>> Oct 29 12:25:39 pdxrs001 kernel: Code: 48 8b 3b e8 c1 9f ff df 48 89 df
>> e8 79 b8 f3 df 48 8b 7d 08
>> Oct 29 12:25:39 pdxrs001 kernel: RIP
>> <ffffffffa0232877>{:drbd:drbd_disconnect+1335} RSP <0000010034393e38>
>> Oct 29 12:25:39 pdxrs001 kernel: CR2: 0000000000000000
>> ~
>>
>> ~
>>
>> on the shell the command respondend with
>>
>>
>> Child process does not terminate!
>> Exiting.
>> pdxrs001:/usr/src/drbd-8.2.0/drbd #
>> pdxrs001:/usr/src/drbd-8.2.0/drbd #
>> pdxrs001:/usr/src/drbd-8.2.0/drbd # No response from the DRBD driver! Is
>> the module loaded?
>> Unconfigured
>>
>>
>> Any idea?
>>
>>
>>
>> Best regards
>>
>>
>> Andre
>>
>>
>>
>> _______________________________________________
>> drbd-user mailing list
>> drbd-user at lists.linbit.com
>> http://lists.linbit.com/mailman/listinfo/drbd-user
>
>
>
--
Mit freundlichen Grüßen
Andre Konopka
Media-Anwendungen
RB Presse-Data GmbH
40196 Düsseldorf
Hausadresse:
Zülpicher Str. 8a Tel: 0211 / 5697- 379
40549 Düsseldorf Fax: 0211 / 5697- 352
E-Mail: Andre.Konopka at Presse-Data.de
Geschäftsführer: Dr. Kay Holzkamp
Sitz Düsseldorf - Amtsgericht Düsseldorf HRB 1944