From: Roman Mamedov <rm@romanrm.net>
To: Andreas Klauer <Andreas.Klauer@metamorpher.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: recovering failed raid5
Date: Sat, 29 Oct 2016 15:29:51 +0500 [thread overview]
Message-ID: <20161029152951.62add3ca@natsu> (raw)
In-Reply-To: <20161028133304.GA11564@metamorpher.de>
On Fri, 28 Oct 2016 15:33:04 +0200
Andreas Klauer <Andreas.Klauer@metamorpher.de> wrote:
> On Fri, Oct 28, 2016 at 01:22:31PM +0100, Alexander Shenkin wrote:
> > One remaining question: is sdc definitely toast?
>
> In my opinion a drive is toast starting from the very first reallocated/
> pending/uncorrectable sector, your drive has several of those and that's
> only the ones the drive already knows about - there may be more.
I'd say you are overly cautious on this. Yes there are drives for which one
reallocated sector is a sign of the coming avalanche of them, but then there
are also ones (e.g. my Hitachi 2TB) which work for years, over than period
develop 3-5-7 reallocated sectors, and THAT'S IT, they just continue to work.
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. (Not to compensate for this, but I
wouldn't be running a 8-10 drive RAID5 in any case).
--
With respect,
Roman
next prev parent reply other threads:[~2016-10-29 10:29 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 [this message]
2016-10-29 12:02 ` Andreas Klauer
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=20161029152951.62add3ca@natsu \
--to=rm@romanrm.net \
--cc=Andreas.Klauer@metamorpher.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.