From: Alfred Isele <Alfred.Isele@fujitsu-siemens.com>
To: Paul Clements <Paul.Clements@SteelEye.com>,
Rob Hagopian <rob@hagopian.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid bug in 2.4.20
Date: Fri, 11 Apr 2003 10:20:33 +0200 [thread overview]
Message-ID: <3.0.6.32.20030411102033.00bafcd0@athen> (raw)
In-Reply-To: <3E961D24.BB595F33@SteelEye.com>
Hello!
Sorry, I have no solution but I'm searching too!
I observed this error with kernel 2.4.19-64GB-SMP (Suse).
We use raid1 with 2 mirrors.
Very often when I detach a mirror by
/mdadm /dev/md0 -f /dev/sda1 -r /dev/sda1
and then reattach it by
/mdadm /dev/md0 -a /dev/sda1
I too get
... speed=0K/sec
After rebooting the resynch really starts.
Moreover sometimes after detaching (... -f ... -r ...)
I have either raid1d or mdrecoveryd
obviously looping uninterruptible on a CPU.
Program top then shows this:
----------------------------------------------------------------------------
----
2:08pm up 4:03, 5 users, load average: 14.23, 14.55, 14.11
226 processes: 219 sleeping, 7 running, 0 zombie, 0 stopped
CPU0 states: 0.0% user, 100.0% system, 0.0% nice, 0.0% idle
CPU1 states: 8.0% user, 13.1% system, 0.0% nice, 78.3% idle
Mem: 1162020K av, 868428K used, 293592K free, 0K shrd, 84904K buff
Swap: 722808K av, 0K used, 722808K free 554484K
cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
20 root 19 0 0 0 0 RW 99.8 0.0 161:14 raid1d
1408 isele 15 0 1112 1112 768 R 5.8 0.0 8:48 top
----------------------------------------------------------------------------
-----
At 21:40 10.04.03 -0400, Paul Clements wrote:
>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
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2003-04-11 8:20 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
2003-04-11 8:20 ` Alfred Isele [this message]
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=3.0.6.32.20030411102033.00bafcd0@athen \
--to=alfred.isele@fujitsu-siemens.com \
--cc=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