linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Paul Clements <Paul.Clements@SteelEye.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid bug in 2.4.20
Date: Fri, 11 Apr 2003 06:10:27 -0400	[thread overview]
Message-ID: <200304110613_MC3-1-33F7-C4B9@compuserve.com> (raw)

Paul Clements wrote:


> Have you been able to reproduce this problem with any regularity? Or
> have you tried? I have an idea what *might* be causing this, if you're
> willing to try out a patch...


 Please post it even if he can't try it.

 All I have found so far is two missing newlines in the status
message code (symptom: lines containing "<6>" in the syslog.)

 (later) just noticed that the raid1 status printout doesn't show the
write_only flag.  This should probably be added...


> BTW, the md "BUG" you originally reported is not really a bug -- that
> always happens when you try to raidhotremove an active disk.


 It calls MD_BUG() when that happens, though.

--
 Chuck
 I am not a number!

             reply	other threads:[~2003-04-11 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 10:10 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-10 22:13 raid bug in 2.4.20 Chuck Ebbert
2003-04-10 22:55 ` Rob Hagopian
2003-04-10 20:05 Rob Hagopian
2003-04-10 20:25 ` Rob Hagopian
2003-04-11  1:40   ` Paul Clements
2003-04-11  8:20     ` Alfred Isele
2003-04-11  9:13       ` Lars Marowsky-Bree
2003-04-11 10:30         ` Alfred Isele

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=200304110613_MC3-1-33F7-C4B9@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=Paul.Clements@SteelEye.com \
    --cc=linux-raid@vger.kernel.org \
    /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).