From: Neil Brown <neilb@cse.unsw.edu.au>
To: Michael Robinton <michael@bizsystems.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: reconstruction stalls
Date: Wed, 17 Jul 2002 08:47:55 +1000 (EST) [thread overview]
Message-ID: <15668.41627.988382.451061@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Michael Robinton on Tuesday July 16
On Tuesday July 16, michael@bizsystems.com wrote:
> i86 2.4.17 kernel
> 2 - 1de 20 gig western digital drives on separate channels (ASUS-me99)
> There are several raid partitions on this drive, one managed to get out of
> sync when the cpu failed. The ext2 file system is fine but the arrray will
> not reconstruct -- I have 7 linux boxes running various flavors or raid 1
> and 5 for several years, and this is the first time I've seen anything
> like this.
>
> The reconstruction proceeds until /proc/mdstat says 99.9% complete
> (2015872,2015936) finish 0.0 min
> then the speed keeps going down with each successive query. There is no
> disk activity per the "red" light. Tried this twice with identical results
> each time.
>
> Any suggestions??
Sounds like a bug that was fixed recently...
It may be that you just need to encourage some other disc activity on
that system and it will spring to life and finish.
NeilBrown
>
> Michael
>
>
> -
> 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:[~2002-07-16 22:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 22:17 reconstruction stalls Michael Robinton
2002-07-16 22:47 ` Neil Brown [this message]
2002-07-17 17:35 ` Couldn't umount on /mnt/md0-device busy??? bo
2002-07-17 18:52 ` Kanoalani Withington
2002-07-18 0:13 ` bo
[not found] ` <009d01c22e54$54d968a0$f6de11cc@black>
2002-07-18 17:11 ` bo
2002-07-18 17:47 ` Ross Vandegrift
2002-07-19 0:43 ` bo
2002-07-19 0:58 ` Ross Vandegrift
2002-07-19 1:49 ` Kanoalani Withington
2002-07-20 8:32 ` Egon Eckert
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=15668.41627.988382.451061@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=linux-raid@vger.kernel.org \
--cc=michael@bizsystems.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;
as well as URLs for NNTP newsgroup(s).