Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Hannes Dorbath
On 28.09.2007 11:00, Laurent CARON wrote: The $HOME directories are stored on a drbd (version: 0.7.24 (api:79/proto:74)) partition (with an XFS filesystem). Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with 2.6.22? -- Regards, Hannes Dorbath - To unsubscribe from this list: send

Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Laurent CARON
Stefan Seifert wrote: > The deadlock also occures with 0.7.x. A patch for that is floating around. Here is a transcript from a mail I sent to Lars Ellenberg It should 'normally' be fixed. Am I wrong ? Thanks On Sun, Sep 16, 2007 at 05:34:01PM +0200, Laurent CARON wrote: > > Lars Ellenberg a

Crash on 2.6.22

2007-09-28 Thread Laurent CARON
Hi, I did experience a quite strange problem (at least for me) on the first node of our 2 node cluster. This is basically an imap/smtp/http proxy server. One of the imapd processes started to use a lot of cpu, memory... this morning. Oomkiller showed up and killed slapd, imapd, amavisd I

Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Stefan Seifert
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hannes Dorbath wrote: > On 28.09.2007 11:00, Laurent CARON wrote: >> The $HOME directories are stored on a drbd (version: 0.7.24 >> (api:79/proto:74)) partition (with an XFS filesystem). > > Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine

Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Laurent CARON
Hannes Dorbath wrote: > On 28.09.2007 11:00, Laurent CARON wrote: >> The $HOME directories are stored on a drbd (version: 0.7.24 >> (api:79/proto:74)) partition (with an XFS filesystem). > > Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with 2.6.22? I only experienced it with 2.6.22.

Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Stefan Seifert
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hannes Dorbath wrote: On 28.09.2007 11:00, Laurent CARON wrote: The $HOME directories are stored on a drbd (version: 0.7.24 (api:79/proto:74)) partition (with an XFS filesystem). Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with

Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Laurent CARON
Hannes Dorbath wrote: On 28.09.2007 11:00, Laurent CARON wrote: The $HOME directories are stored on a drbd (version: 0.7.24 (api:79/proto:74)) partition (with an XFS filesystem). Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with 2.6.22? I only experienced it with 2.6.22. Since

Crash on 2.6.22

2007-09-28 Thread Laurent CARON
Hi, I did experience a quite strange problem (at least for me) on the first node of our 2 node cluster. This is basically an imap/smtp/http proxy server. One of the imapd processes started to use a lot of cpu, memory... this morning. Oomkiller showed up and killed slapd, imapd, amavisd I

Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Laurent CARON
Stefan Seifert wrote: The deadlock also occures with 0.7.x. A patch for that is floating around. Here is a transcript from a mail I sent to Lars Ellenberg It should 'normally' be fixed. Am I wrong ? Thanks On Sun, Sep 16, 2007 at 05:34:01PM +0200, Laurent CARON wrote: Lars Ellenberg a

Re: [DRBD-user] Crash on 2.6.22

2007-09-28 Thread Hannes Dorbath
On 28.09.2007 11:00, Laurent CARON wrote: The $HOME directories are stored on a drbd (version: 0.7.24 (api:79/proto:74)) partition (with an XFS filesystem). Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with 2.6.22? -- Regards, Hannes Dorbath - To unsubscribe from this list: send

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-16 Thread David Miller
From: [EMAIL PROTECTED] (Linas Vepstas) Date: Mon, 16 Jul 2007 12:25:35 -0500 > On Fri, Jul 13, 2007 at 03:47:02PM -0700, David Miller wrote: > > From: [EMAIL PROTECTED] (Linas Vepstas) > > Date: Fri, 13 Jul 2007 15:05:15 -0500 > > > > > > > > This is a patch (& bug report) for a crash in

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-16 Thread Linas Vepstas
On Fri, Jul 13, 2007 at 03:47:02PM -0700, David Miller wrote: > From: [EMAIL PROTECTED] (Linas Vepstas) > Date: Fri, 13 Jul 2007 15:05:15 -0500 > > > > > This is a patch (& bug report) for a crash in sysctl_set_parent() > > in 2.6.22-git2. > > > > Problem: 2.6.22-git2 crashes with a stack

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-16 Thread Linas Vepstas
On Fri, Jul 13, 2007 at 07:06:56PM -0600, Eric W. Biederman wrote: > > .data = _devconf.loop, > > .maxlen = sizeof(int), > > .mode = 0644, > > + .child = 0x0, > >

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-16 Thread Linas Vepstas
On Fri, Jul 13, 2007 at 07:06:56PM -0600, Eric W. Biederman wrote: .data = ipv4_devconf.loop, .maxlen = sizeof(int), .mode = 0644, + .child = 0x0, .proc_handler

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-16 Thread Linas Vepstas
On Fri, Jul 13, 2007 at 03:47:02PM -0700, David Miller wrote: From: [EMAIL PROTECTED] (Linas Vepstas) Date: Fri, 13 Jul 2007 15:05:15 -0500 This is a patch ( bug report) for a crash in sysctl_set_parent() in 2.6.22-git2. Problem: 2.6.22-git2 crashes with a stack trace

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-16 Thread David Miller
From: [EMAIL PROTECTED] (Linas Vepstas) Date: Mon, 16 Jul 2007 12:25:35 -0500 On Fri, Jul 13, 2007 at 03:47:02PM -0700, David Miller wrote: From: [EMAIL PROTECTED] (Linas Vepstas) Date: Fri, 13 Jul 2007 15:05:15 -0500 This is a patch ( bug report) for a crash in sysctl_set_parent()

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread Eric W. Biederman
[EMAIL PROTECTED] (Linas Vepstas) writes: > This is a patch (& bug report) for a crash in sysctl_set_parent() > in 2.6.22-git2. > > Problem: 2.6.22-git2 crashes with a stack trace > [c1d0fb00] c0067b4c .sysctl_set_parent+0x48/0x7c > [c1d0fb90] c0069b40

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread Satyam Sharma
Hi, I'm totally confuzed by this patch ... On 7/14/07, Linas Vepstas <[EMAIL PROTECTED]> wrote: This is a patch (& bug report) for a crash in sysctl_set_parent() in 2.6.22-git2. Are you sure you saw this crash on 22-git2 (Linus' tree) ??? Problem: 2.6.22-git2 crashes with a stack trace

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread David Miller
From: [EMAIL PROTECTED] (Linas Vepstas) Date: Fri, 13 Jul 2007 15:05:15 -0500 > > This is a patch (& bug report) for a crash in sysctl_set_parent() > in 2.6.22-git2. > > Problem: 2.6.22-git2 crashes with a stack trace > [c1d0fb00] c0067b4c .sysctl_set_parent+0x48/0x7c >

[PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread Linas Vepstas
This is a patch (& bug report) for a crash in sysctl_set_parent() in 2.6.22-git2. Problem: 2.6.22-git2 crashes with a stack trace [c1d0fb00] c0067b4c .sysctl_set_parent+0x48/0x7c [c1d0fb90] c0069b40 .register_sysctl_table+0x7c/0xf4 [c1d0fc30]

[PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread Linas Vepstas
This is a patch ( bug report) for a crash in sysctl_set_parent() in 2.6.22-git2. Problem: 2.6.22-git2 crashes with a stack trace [c1d0fb00] c0067b4c .sysctl_set_parent+0x48/0x7c [c1d0fb90] c0069b40 .register_sysctl_table+0x7c/0xf4 [c1d0fc30]

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread David Miller
From: [EMAIL PROTECTED] (Linas Vepstas) Date: Fri, 13 Jul 2007 15:05:15 -0500 This is a patch ( bug report) for a crash in sysctl_set_parent() in 2.6.22-git2. Problem: 2.6.22-git2 crashes with a stack trace [c1d0fb00] c0067b4c .sysctl_set_parent+0x48/0x7c

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread Satyam Sharma
Hi, I'm totally confuzed by this patch ... On 7/14/07, Linas Vepstas [EMAIL PROTECTED] wrote: This is a patch ( bug report) for a crash in sysctl_set_parent() in 2.6.22-git2. Are you sure you saw this crash on 22-git2 (Linus' tree) ??? Problem: 2.6.22-git2 crashes with a stack trace

Re: [PATCH] crash in 2.6.22-git2 sysctl_set_parent()

2007-07-13 Thread Eric W. Biederman
[EMAIL PROTECTED] (Linas Vepstas) writes: This is a patch ( bug report) for a crash in sysctl_set_parent() in 2.6.22-git2. Problem: 2.6.22-git2 crashes with a stack trace [c1d0fb00] c0067b4c .sysctl_set_parent+0x48/0x7c [c1d0fb90] c0069b40