From: Wols Lists <antlists@youngman.org.uk>
To: Bruce Merry <bmerry@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: What to do about Offline_Uncorrectable and Pending_Sector in RAID1
Date: Mon, 14 Nov 2016 15:58:23 +0000 [thread overview]
Message-ID: <5829DF1F.7030109@youngman.org.uk> (raw)
In-Reply-To: <CAHy4j_7aC+DCqMRkmK12HPP-wY5kAmLf7W3UG_Nn=TK7ry7ARQ@mail.gmail.com>
On 14/11/16 15:52, Bruce Merry wrote:
> On 13 November 2016 at 23:06, Wols Lists <antlists@youngman.org.uk> wrote:
>> > Sounds like that drive could need replacing. I'd get a new drive and do
>> > that as soon as possible - use the --replace option of mdadm - don't
>> > fail the old drive and add the new.
> Would you mind explaining why I should use --replace instead of taking
> out the suspect drive? I guess I lose redundancy for any writes that
> occur while the rebuild is happening, but I'd plan to do this with the
> filesystem unmounted so there wouldn't be any writes.
Because a replace will copy from the old drive to the new, recovering
any failures from the rest of the array. A fail-and-add will have to
rebuild the entire new array from what's left of the old, stressing the
old array much more.
Okay, in your case, it probably won't make an awful lot of difference,
but it does make you vulnerable to problems on the "good" drive. To
alter your wording slightly, you lose redundancy for writes AND READS
that occur while the array is rebuilding. It's just good practice (and I
point it out because --replace is new and not well known at present).
Cheers,
Wol
next prev parent reply other threads:[~2016-11-14 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 18:46 What to do about Offline_Uncorrectable and Pending_Sector in RAID1 Bruce Merry
2016-11-13 20:18 ` Anthony Youngman
2016-11-13 20:51 ` Bruce Merry
2016-11-13 21:06 ` Wols Lists
2016-11-13 23:03 ` Phil Turmel
2016-11-14 6:50 ` Bruce Merry
2016-11-14 16:01 ` Phil Turmel
2016-11-14 16:09 ` Bruce Merry
2016-11-14 16:14 ` Phil Turmel
2016-11-14 15:52 ` Bruce Merry
2016-11-14 15:58 ` Wols Lists [this message]
2016-11-14 16:03 ` Bruce Merry
2016-11-14 16:09 ` Wols Lists
2016-11-14 16:10 ` Phil Turmel
2016-11-15 18:14 ` Peter Sangas
2016-11-15 18:49 ` Anthony Youngman
2016-11-15 19:22 ` Peter Sangas
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=5829DF1F.7030109@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=bmerry@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.