From: Paul Clements <Paul.Clements@SteelEye.com>
To: Rob Hagopian <rob@hagopian.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid bug in 2.4.20
Date: Thu, 10 Apr 2003 21:40:52 -0400 [thread overview]
Message-ID: <3E961D24.BB595F33@SteelEye.com> (raw)
In-Reply-To: Pine.LNX.4.44.0304101623300.25209-100000@karma.hagopian.net
Hi,
Rob Hagopian wrote:
> Personalities : [linear] [raid0] [raid1] [raid5]
> read_ahead 1024 sectors
> md7 : active raid1 sdb6[2] sda6[0]
> 1052160 blocks [2/1] [U_]
>
> md0 : active raid1 sdb1[2] sda1[0]
> 128384 blocks [2/1] [U_]
> [>....................] recovery = 0.0% (0/128384)
> finish=3658.9min speed=0K/sec
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...
BTW, the md "BUG" you originally reported is not really a bug -- that
always happens when you try to raidhotremove an active disk.
--
Paul
next prev parent reply other threads:[~2003-04-11 1:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 20:05 raid bug in 2.4.20 Rob Hagopian
2003-04-10 20:25 ` Rob Hagopian
2003-04-11 1:40 ` Paul Clements [this message]
2003-04-11 8:20 ` Alfred Isele
2003-04-11 9:13 ` Lars Marowsky-Bree
2003-04-11 10:30 ` Alfred Isele
2003-04-10 23:02 ` Question: Adding another IDE controller jeff millar
2003-04-11 23:12 ` Changing Drive letters jeff millar
2003-04-11 23:41 ` Neil Brown
2003-04-12 1:48 ` jeff millar
2003-04-12 2:01 ` Mads Peter Bach
2003-04-12 2:29 ` Neil Brown
2003-04-12 19:06 ` Mr. James W. Laferriere
2003-04-12 21:19 ` Neil Brown
2003-04-12 22:15 ` Mr. James W. Laferriere
-- 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-11 10:10 Chuck Ebbert
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=3E961D24.BB595F33@SteelEye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=rob@hagopian.net \
/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).