linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Waldo <pwaldo@waldoware.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Kernel panic during resync
Date: Tue, 15 Aug 2006 12:12:01 -0400	[thread overview]
Message-ID: <44E1F251.9040808@waldoware.com> (raw)
In-Reply-To: <17632.62892.429563.800085@cse.unsw.edu.au>

Neil Brown wrote:
> On Friday August 11, pwaldo@waldoware.com wrote:
>> Hi all,
>>
>> I've got a machine with a RAID6 array which hung on me yesterday.  Upon
>> reboot, mdadm refused to start the array, since it was degraded and
>> dirty.  The array had 7 drives, and one had previously gone bad.  I'm
>> running Fedora Core 5.
>>
>> I rebooted, using the "md-mod.start_dirty_degraded=1" parameter.
>> Everything seemed to be OK--the sync process started and I watched it go
>> for about half an hour.  I came back later, and found the machine had a
>> kernel panic with the message "Kernel panic - not syncing: Fatal
>> exception in interrupt".  Just to make sure, I restarted and tried to
>> sync again, but got the same message.
>>
>> What might be causing this?  Is there any way to recover?  Thanks in
>> advance!
> 
> It is very hard to say without more details.
> Was there any stack trace?  Any other possibly related messages that
> you can report?
> 
> And what kernel (exactly) are you using?
> 
> NeilBrown

Hi Niel,

Thanks for the reply.  I resolved the issue by using a different disk. 
I had a suspicion that the disk might have some problems, but I figured 
that the sync process would work around it and give at least a warning 
or give me a message saying that the disk was unusable.  I wasn't 
expecting a panic :-O

My recollection of the stack trace was the problem was in a 
raid6-buffer-flush type of place.  Sorry I don't have any more info for 
you...

Paul

      reply	other threads:[~2006-08-15 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 13:08 Kernel panic during resync Paul Waldo
2006-08-14 22:14 ` Neil Brown
2006-08-15 16:12   ` Paul Waldo [this message]

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=44E1F251.9040808@waldoware.com \
    --to=pwaldo@waldoware.com \
    --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).