From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: recovering failed raid5
Date: Sat, 29 Oct 2016 14:02:30 +0200 [thread overview]
Message-ID: <20161029120230.GA4725@metamorpher.de> (raw)
In-Reply-To: <20161029152951.62add3ca@natsu>
On Sat, Oct 29, 2016 at 03:29:51PM +0500, Roman Mamedov wrote:
> And if there's an unreadable sector on rebuild as a drive found its 8th bad
> sector after 3 more years of perfect operation, that's not a problem either,
> because the setup they run in, is RAID6.
But if such disks are acceptable to run in a RAID, and you advertize it
as such, you have to expect to see RAIDs where every single disk has a
dozen reallocated sectors and a history of read errors to go with it.
Is that still fine? Do you expect to be lucky every time?
RAID-6 is not magic, either. Sooner or later, it will fail, too.
Keep ignoring errors in RAID-5 and you'll see double failure.
Keep ignoring errors in RAID-6 long enough and you'll see triple failure.
All disks fail and many of them do silently, undetected if untested.
If you rented a server in a datacenter, thus entitled to working hardware,
would you create a ticket on read failure or not?
Regards
Andreas Klauer
next prev parent reply other threads:[~2016-10-29 12:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 15:06 recovering failed raid5 Alexander Shenkin
2016-10-27 16:04 ` Andreas Klauer
2016-10-28 12:22 ` Alexander Shenkin
2016-10-28 13:33 ` Andreas Klauer
2016-10-28 21:16 ` Phil Turmel
2016-10-28 23:45 ` Andreas Klauer
2016-10-29 2:52 ` Edward Kuns
2016-10-29 2:53 ` Phil Turmel
2016-10-29 8:46 ` Mikael Abrahamsson
2016-10-29 10:29 ` Roman Mamedov
2016-10-29 12:02 ` Andreas Klauer [this message]
2016-10-30 16:18 ` Phil Turmel
2016-10-28 13:36 ` Robin Hill
2016-10-31 10:44 ` Alexander Shenkin
2016-10-31 11:09 ` Andreas Klauer
2016-10-31 15:19 ` Robin Hill
2016-10-31 16:26 ` Wols Lists
2016-10-31 16:28 ` Wols Lists
2016-11-16 9:04 ` Alexander Shenkin
2016-11-16 11:14 ` Andreas Klauer
2016-11-16 13:27 ` Alexander Shenkin
2016-11-16 13:59 ` Andreas Klauer
2016-11-16 15:35 ` Wols Lists
2016-11-16 15:50 ` Alexander Shenkin
2016-11-16 16:38 ` Wols Lists
2017-01-05 12:08 ` Alexander Shenkin
2016-10-31 16:31 ` Wols Lists
2016-10-27 16:26 ` Roman Mamedov
2016-10-27 20:34 ` Robin Hill
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=20161029120230.GA4725@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
/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.