From: "Otto Meier" <gf435@gmx.net>
To: "Neil Brown" <neilb@cse.unsw.edu.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Kernel crash during resync of raid5 on SMP
Date: Thu, 08 Mar 2001 16:19:50 +0100 [thread overview]
Message-ID: <200103081519.f28FJ9u05622@gate2.private.net> (raw)
In-Reply-To: <15014.44624.26763.798524@notabene.cse.unsw.edu.au>
On Thu, 8 Mar 2001 08:55:28 +1100 (EST), Neil Brown wrote:
>On Wednesday March 7, gf435@gmx.net wrote:
>> I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
>> in degraded mode. Today I put in a new disk to switch to
>> full raid5 mode. Shortly after the command raidhotadd the
>> system crashed with the message lost interrupt on cpu1.
>
>Was there an Oops? Can we see? decoded with ksymoops of course.
Unfortunatly I entered this command remotely. The console Display was
off at that time.
>Are you happy to retry? (i.e. raidsetfaulty; raidhotremove,
>raidhotadd). If so, Could you try with 2.4.2?
I would not really like to do that, as of now everything runs fine again for a day.
>Where abouts in the sync-process did it die? Start? end? middle?
>various?
After the first crash I needed to reboot. It crashed again shortly after
boot message that it starts to resync.
This happens several times until I used the kernel parameter MAXcpus=1.
Then it worked without a problem. After resyncing finished I could start
it again in SMP mode and everything worked fine again.
Sorry that can not shed any more light on it.
Otto
>NeilBrown
>
>
>>
>> This continued after reboot. I finaly managed to get it running again
>> by booting with kernel parameter maxcpus=1. In this one CPU mode
>> it finished resycing.
>>
>> During this process I was never able to resync with two CPU's.
>>
>> After finishing rescyncing the system run now fine in SMP Dual mode again.
>>
>> Perhaps there might be an issue with spinlocks during resyncing.
>>
>> Bye Otto
>>
>>
>>
>>
>>
>>
>
next prev parent reply other threads:[~2001-03-08 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 20:47 [PATCH] - filesystem corruption on soft RAID5 in 2.4.0+ Neil Brown
2001-01-21 21:14 ` Manfred Spraul
2001-01-22 11:19 ` Holger Kiehl
2001-01-22 9:23 ` Hans Reiser
2001-01-22 19:36 ` Edward
2001-01-23 8:21 ` Holger Kiehl
2001-03-07 21:30 ` Kernel crash during resync of raid5 on SMP Otto Meier
2001-03-07 21:55 ` Neil Brown
2001-03-08 15:19 ` Otto Meier [this message]
2001-03-09 0:17 ` Neil Brown
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=200103081519.f28FJ9u05622@gate2.private.net \
--to=gf435@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
Powered by JetHome