linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jose Manuel dos Santos Calhariz <jose.spam@netvisao.pt>
To: NeilBrown <neilb@suse.de>
Cc: jose.spam@netvisao.pt, linux-raid@vger.kernel.org
Subject: Re: linux-image-2.6.32-5-686: kernel BUG at ... build/source_i386_none/drivers/md/raid5.c:2764!
Date: Sun, 24 Jun 2012 18:02:34 +0100	[thread overview]
Message-ID: <20120624170234.GA13154@calhariz.com> (raw)
In-Reply-To: <20120624182146.7d63fbbb@notabene.brown>

[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]

On Sun, Jun 24, 2012 at 06:21:46PM +1000, NeilBrown wrote:
> On Fri, 22 Jun 2012 13:19:53 +0100 Jose Manuel dos Santos Calhariz
> <jose.spam@netvisao.pt> wrote:
> 
> > 
> > In another day during the periodic mdadm RAID check: 
> >  - the linux kernel gave a kernel BUG, 
> >  - tried to kick out a failed disk and 
> >  - stopped accepting I/O to the affected raid.  
> > 
> > The affected programs were in state D.  The only way to recover was to
> > do a reboot.  After reboot the problematic disk was replaced.
> > 
> > I reported the bug to Debian and is there all the information about it:
> > 
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675969
> > 
> > I was asked to report the BUG here in case someone knows what happened.
> > 
> > Here is a summary of the more relevant information:
> > 
> > This machine have 2 x RAID6 with 6 disks each, for a total of 12 disks. 
> > 
> > I have 5 systems with a similar setup and only one failed, maybe
> > because of the failing disk.  I will use one of the systems to try to
> > reproduce the bug, before triyng a new kernel.
> > 
> > 
> > The proprietary module is the openafs filesystem v1.6.1 backported
> > from Debian testing.
> > 
> > The kernel bug is:
> > 
> > 
> > build/source_i386_none/drivers/md/raid5.c:2764!

> 
> This bug was fixed in 2.6.32.49 and 3.2
> 
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=61d433c479a6ccfed6a7e73e6111ca8fa0348c63
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=9a3f530f39f4490eaa18b02719fb74ce5f4d2d86
> 
> NeilBrown

The failing kernel had that fix all ready.  The machine was running
the kernel Debian 2.6.32-41squeeze2.  Looking into the change log,
this kernel have all the fixes until 2.6.32.51 plus other fixes.

     Jose Calhariz

-- 
--

Ambição: um supremo desejo de ser vilipendiado por seus inimigos enquanto você está vivo e ser ridicularizado pelos amigos quando estiver morto

--Ambrose Bierce

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-06-24 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 12:19 linux-image-2.6.32-5-686: kernel BUG at ... build/source_i386_none/drivers/md/raid5.c:2764! Jose Manuel dos Santos Calhariz
2012-06-24  8:21 ` NeilBrown
2012-06-24 17:02   ` Jose Manuel dos Santos Calhariz [this message]
2012-06-25  2:39     ` NeilBrown
2012-06-25  2:58       ` Christian Balzer
2012-06-25  6:42         ` NeilBrown
2012-06-25  6:55           ` Christian Balzer
2012-06-25 10:59           ` Jose Manuel dos Santos Calhariz
     [not found]             ` <CAGqmV7rBk9R-q-LRVw1tzxmXoQMLTQbQY8f9C0SOuaMOf7AfoQ@mail.gmail.com>
2012-06-27 14:12               ` Jose Manuel dos Santos Calhariz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120624170234.GA13154@calhariz.com \
    --to=jose.spam@netvisao.pt \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).