From: Ross Vandegrift <ross@willow.seitz.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mirror recovery?
Date: Thu, 20 Jun 2002 22:56:47 -0400 [thread overview]
Message-ID: <20020621025647.GA943@willow.seitz.com> (raw)
In-Reply-To: <15634.37559.635719.855683@notabene.cse.unsw.edu.au>
> > 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.
Ok, I wasn't sure if the second failure during reconstruction was
disastrous for RAID1. Looks like it's not - my boss lent me a disk to
use until my RMA'ed Deathstar comes in, and as soon as I hot added a new
partition, reconstruction started with all my data.
Somedays when the simple things go right it's enough to make your day
::-)
> 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".
Hardly a biased opinion. I've seen more than my share of IDE disk
failures at work - it's always the IDE driver that falls over first.
Ross Vandegrift
ross@willow.seitz.com
prev parent reply other threads:[~2002-06-21 2:56 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
2002-06-21 2:56 ` Ross Vandegrift [this message]
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=20020621025647.GA943@willow.seitz.com \
--to=ross@willow.seitz.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).