From: Wols Lists <antlists@youngman.org.uk>
To: David Brown <david.brown@hesbynett.no>,
Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Reindl Harald <h.reindl@thelounge.net>,
Jeff Allison <jeff.allison@allygray.2y.net>,
Adam Goryachev <mailinglists@websitemanagers.com.au>,
linux-raid@vger.kernel.org
Subject: Re: proactive disk replacement
Date: Tue, 21 Mar 2017 15:31:48 +0000 [thread overview]
Message-ID: <58D14764.60909@youngman.org.uk> (raw)
In-Reply-To: <58D1381E.1080101@hesbynett.no>
On 21/03/17 14:26, David Brown wrote:
> It is possible that if there are a large number of UREs from a drive,
> that the RAID system will consider the whole drive bad and drop it. But
> other than that, UREs will be treated independently.
Doesn't mdadm have a setting that does exactly that? Too many UREs and
the drive gets dropped? I'm sure I've come across that interfering with
rebuilds.
Cheers,
Wol
next prev parent reply other threads:[~2017-03-21 15:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 12:47 proactive disk replacement Jeff Allison
2017-03-20 13:25 ` Reindl Harald
2017-03-20 14:59 ` Adam Goryachev
2017-03-20 15:04 ` Reindl Harald
2017-03-20 15:23 ` Adam Goryachev
2017-03-20 16:19 ` Wols Lists
2017-03-21 2:33 ` Jeff Allison
2017-03-21 9:54 ` Reindl Harald
2017-03-21 10:54 ` Adam Goryachev
2017-03-21 11:03 ` Reindl Harald
2017-03-21 11:34 ` Andreas Klauer
2017-03-21 12:03 ` Reindl Harald
2017-03-21 12:41 ` Andreas Klauer
2017-03-22 4:16 ` NeilBrown
2017-03-21 11:56 ` Adam Goryachev
2017-03-21 12:10 ` Reindl Harald
2017-03-21 13:13 ` David Brown
2017-03-21 13:24 ` Reindl Harald
2017-03-21 14:15 ` David Brown
2017-03-21 15:25 ` Wols Lists
2017-03-21 15:41 ` David Brown
2017-03-21 16:49 ` Phil Turmel
2017-03-22 13:53 ` Gandalf Corvotempesta
2017-03-22 14:12 ` David Brown
2017-03-22 14:32 ` Phil Turmel
2017-03-21 11:55 ` Gandalf Corvotempesta
2017-03-21 13:02 ` David Brown
2017-03-21 13:26 ` Gandalf Corvotempesta
2017-03-21 14:26 ` David Brown
2017-03-21 15:31 ` Wols Lists [this message]
2017-03-21 17:00 ` Phil Turmel
2017-03-21 15:29 ` Wols Lists
2017-03-21 16:55 ` Phil Turmel
2017-03-22 14:51 ` John Stoffel
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=58D14764.60909@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=david.brown@hesbynett.no \
--cc=gandalf.corvotempesta@gmail.com \
--cc=h.reindl@thelounge.net \
--cc=jeff.allison@allygray.2y.net \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.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).