From: Ross Dickson <ross@datscreative.com.au>
To: preining@logic.at
Cc: linux-kernel@vger.kernel.org
Subject: Re: md raid oops on 2.4.25/alpha
Date: Mon, 29 Mar 2004 02:45:51 +1000 [thread overview]
Message-ID: <200403290245.51813.ross@datscreative.com.au> (raw)
Norbert Preining wrote
> Hi Ingo, hi Neil, hi lists!
> We have some problems with the md code on alpha. We get regular oops
> when using the md raid1. Here we got another oops when fsck (at boot
> time) the raid:
> This was after a fresh reboot. As long as only the raid is *not* mounted
> of fsck the machine works without any oops.
Please clarify symptoms regarding fsck at boot and Oops. Are they like mine?
Symptoms I have had with a compact flash boot hda (ide) are that
clean boot with fsck doing nothing is OK no Oops.
If fsck corrects anything and boot continues then Oops will occur. That is I
need to reboot machine after fsck rc=1 or I get Oops.
Regards
Ross.
> I also can mount the hard disks *without* raid directly as hda1 and
> hdc1, and do NOT get any errors here, so I suspect that only the md code
> is the culprit.
> Please tell me how I can track down this problem, how I can help you!
next prev reply other threads:[~2004-03-28 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 14:13 Transmit timeout with 3c395, 2.4.19, 2.4.22 Norbert Preining
2003-10-27 19:18 ` Andrew Morton
2003-10-28 6:49 ` Norbert Preining
2003-10-30 17:50 ` Stian Jordet
2004-03-27 16:41 ` Oops with md/ext3 on 2.4.25 on alpha architecture Norbert Preining
2004-03-28 16:02 ` md raid oops on 2.4.25/alpha Norbert Preining
2004-03-28 17:30 ` Thomas Steudten
2004-03-28 16:45 ` Ross Dickson [this message]
2004-03-28 20:32 ` Norbert Preining
2004-03-28 18:30 ` Ivan Kokshaysky
2004-03-29 10:41 ` Thomas Steudten
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 6:53 Lewis Shobbrook
2004-04-02 12:03 ` Marcelo Tosatti
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=200403290245.51813.ross@datscreative.com.au \
--to=ross@datscreative.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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