From: Phil Turmel <philip@turmel.org>
To: Chris <email.bug@arcor.de>, linux-raid@vger.kernel.org
Subject: Re: re-add POLICY
Date: Mon, 16 Feb 2015 08:17:30 -0500 [thread overview]
Message-ID: <54E1EDEA.1030503@turmel.org> (raw)
In-Reply-To: <loom.20150216T124230-883@post.gmane.org>
Hi Chris,
On 02/16/2015 07:23 AM, Chris wrote:
> .... with raid members that got pulled and are save to
> re-sync. (e.g. after the occasional bad block error that gets remapped by
> the hardrives firmware)
This should not be part of your concern here, as MD will handle
occassional UREs by reconstructing them and rewriting them on the fly,
-- without failing the device. If devices are failing after read
errors, you have a different problem. (Hint: look at recent threads
for "timeout mismatch".)
Phil
next prev parent reply other threads:[~2015-02-16 13:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 21:59 re-add POLICY Chris
2015-02-15 19:03 ` re-add POLICY: conflict detection? Chris
2015-02-16 3:28 ` re-add POLICY NeilBrown
2015-02-16 12:23 ` Chris
2015-02-16 13:17 ` Phil Turmel [this message]
2015-02-16 16:15 ` desktop disk's error recovery timouts (was: re-add POLICY) Chris
2015-02-16 17:19 ` desktop disk's error recovery timouts Phil Turmel
2015-02-16 17:48 ` What are mdadm maintainers to do? (was: desktop disk's error recovery timeouts) Chris
2015-02-16 19:44 ` What are mdadm maintainers to do? Phil Turmel
2015-02-16 23:49 ` What are mdadm maintainers to do? (was: desktop disk's error recovery timeouts) NeilBrown
2015-02-17 7:52 ` What are mdadm maintainers to do? (error recovery redundancy/data loss) Chris
2015-02-17 8:48 ` Mikael Abrahamsson
2015-02-17 10:37 ` Chris
2015-02-17 19:33 ` Chris Murphy
2015-02-17 22:47 ` Adam Goryachev
2015-02-18 1:02 ` Chris Murphy
2015-02-18 11:04 ` Chris
2015-02-19 6:12 ` Chris Murphy
2015-02-20 5:12 ` Roger Heflin
2015-02-17 23:33 ` Chris
2015-02-18 15:04 ` help with the little script (erc timout fix) Chris
2015-02-18 21:25 ` NeilBrown
2015-02-17 15:09 ` re-add POLICY Chris
2015-02-22 13:23 ` Chris
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=54E1EDEA.1030503@turmel.org \
--to=philip@turmel.org \
--cc=email.bug@arcor.de \
--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.