From: Lars Marowsky-Bree <lmb@suse.de>
To: war <war@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.20 Raid Bug?
Date: Sun, 30 Mar 2003 12:05:42 +0200 [thread overview]
Message-ID: <20030330100541.GA3798@marowsky-bree.de> (raw)
In-Reply-To: <Pine.LNX.4.51.0303291657550.16794@p300>
On 2003-03-29T16:58:29,
war <war@lucidpixels.com> said:
> Before I even configured it, this showed up.
> How is that relevant?
Because you did not mention it before at all. There was no way of knowing
whether you used a special RAID configuration which triggered the problem.
In any case, I cannot reproduce it. Maybe you should try the latest .21pre
kernel instead, perhaps its doing better for you?
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
SuSE Labs - Research & Development, SuSE Linux AG
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
-- Capt. Edward A. Murphy -- Louis Pasteur
prev parent reply other threads:[~2003-03-30 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 21:03 Linux 2.4.20 Raid Bug? war
2003-03-29 21:41 ` Lars Marowsky-Bree
2003-03-29 21:45 ` war
2003-03-29 21:56 ` Lars Marowsky-Bree
2003-03-29 21:58 ` war
2003-03-30 10:05 ` Lars Marowsky-Bree [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=20030330100541.GA3798@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=war@lucidpixels.com \
/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