From: Neil Brown <neilb@cse.unsw.edu.au>
To: Ross Vandegrift <ross@willow.seitz.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mirror recovery?
Date: Fri, 21 Jun 2002 12:43:03 +1000 (EST) [thread overview]
Message-ID: <15634.37559.635719.855683@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Ross Vandegrift on Thursday June 20
On Thursday June 20, ross@willow.seitz.com wrote:
> Hello all,
>
> Lost a drive in my box last night - woke up to it locked
> completely solid. So I reset the machine, it started to come back up
> and remirror the drives. I set about trying to figure out why it locked
> (the terminal had blanked overnight of course, and wouldn't unblank so
> I missed the probable standard failure messages). Then the box locked
> hard again, right as I heard one of my IDE drives make some terrible
> noises.
Don't you hate that noise...
>
> So I rebooted, and ran the manufacturer's disk test, sure enough
> it's headed south. Once I've got a replacement drive, will I be able to
> get the data on my raid partition back? I don't think I've ever had a
> failure happen on a RAID1 array during resync. Once on RAID5, and that
> was a disaster....
You shouldn't have any problems getting your data back. Indeed you
should be able to get it even before the new drives arrive, that is
what RAID is about.
My (biased) guess is that the machine locked up because the IDE driver
was not coping elegantly with the drive failure.
I think it would be nice if the raid system could tell the device "if
you get an error, don't retry too hard, I'm happy to cope".
NeilBrown
next prev parent reply other threads:[~2002-06-21 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 14:01 Mirror recovery? Ross Vandegrift
2002-06-21 2:43 ` Neil Brown [this message]
2002-06-21 2:56 ` Ross Vandegrift
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=15634.37559.635719.855683@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=linux-raid@vger.kernel.org \
--cc=ross@willow.seitz.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).