Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Roman Mamedov <rm@romanrm.net>, Reindl Harald <h.reindl@thelounge.net>
Cc: Wols Lists <antlists@youngman.org.uk>,
	Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
	Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: 3 way mirror
Date: Mon, 12 Sep 2022 09:02:17 -0400	[thread overview]
Message-ID: <1f778c1f-6767-e581-0846-505edf01ed68@turmel.org> (raw)
In-Reply-To: <20220912142624.63ba4b5c@nvm>

On 9/12/22 05:26, Roman Mamedov wrote:
> On Mon, 12 Sep 2022 10:16:55 +0200
> Reindl Harald <h.reindl@thelounge.net> wrote:
> 
>>> That's called paranoia
>>
>> that's called common sense
>>
>>> ALL drives have hiccups when there's absolutely
>>> nothing wrong with them. What are the manufacturer's error figures?
>>> Expect at least one error every two or three complete passes of pretty
>>> much every large big disk nowadays?
>> i don't expect any SMART error at all and if one hits after years of
>> uptime fine that the drive don't fail completly - but would i trust it? no!
> 
> I have multiple drives (Hitachi) which have developed around 3 to 10
> reallocated sectors, and then just continue to work for years, not increasing
> those further. Throwing them away would be uneconomical. Not always a
> reallocated sector is a sign of impeding failure, what you need to look for is
> if there is more than one, and the count is increasing quickly.

Concur. I do not replace drives for reallocated sectors until they reach 
double digits.  Modern drives are expected to do this.

> Generally though, if you are way too concerned about individual drive failures,
> it could be a sign that you do not have a robust enough backup scheme in place.

Heh.

Phil


      parent reply	other threads:[~2022-09-12 13:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11  9:08 3 way mirror Gandalf Corvotempesta
2022-09-11  9:50 ` Geoff Back
2022-09-11 10:08 ` Wols Lists
2022-09-11 10:21   ` Gandalf Corvotempesta
2022-09-12  0:58   ` Phil Turmel
2022-09-12  8:06     ` Wols Lists
2022-09-12 12:48       ` Phil Turmel
2022-09-11 10:52 ` Reindl Harald
2022-09-11 11:35   ` Gandalf Corvotempesta
2022-09-11 12:20     ` Reindl Harald
2022-09-11 18:08       ` Wols Lists
2022-09-11 19:11         ` Gandalf Corvotempesta
2022-09-12  8:16         ` Reindl Harald
2022-09-12  8:18           ` Gandalf Corvotempesta
2022-09-12  9:26           ` Roman Mamedov
2022-09-12  9:40             ` Reindl Harald
2022-09-12 13:02             ` Phil Turmel [this message]

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=1f778c1f-6767-e581-0846-505edf01ed68@turmel.org \
    --to=philip@turmel.org \
    --cc=antlists@youngman.org.uk \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=h.reindl@thelounge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox