Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>,
	Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: 3 way mirror
Date: Sun, 11 Sep 2022 19:08:04 +0100	[thread overview]
Message-ID: <2bcebfce-6def-38f8-99be-1f5702905f94@youngman.org.uk> (raw)
In-Reply-To: <dcef59a2-b8f6-ef8b-2fd6-2c8bfdfba4ad@thelounge.net>

On 11/09/2022 13:20, Reindl Harald wrote:
> 
> 
> Am 11.09.22 um 13:35 schrieb Gandalf Corvotempesta:
>> Il giorno dom 11 set 2022 alle ore 12:52 Reindl Harald
>> <h.reindl@thelounge.net> ha scritto:
>>> just throw it out of the array - on a RAID 1 with two disk you have
>>> still redundancy and i won't trust a disk which recognized that it has
>>> errors on it's own
>>
>> Why ? if it's just a single sector, the rest of the disk could be used
>> properly until the replacement.
> 
> i simply don't trust drives which have thrown errors
> you don't lose anything when you push it out of the array

That's called paranoia - 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?

What's the point of having thousands of spare sectors, if you chuck the 
drive in the trash at the first hint of trouble?
> 
>>> what's the point of "can i delay" when you have no other options? :-)
>>
>> The option is: i've ordered the new disk, it should arrive this thursday.
>> If i'm still on the safe side, i'll wait, if not, i'll replace with
>> the first disk I have here, even if slower
> 
> you are clearly on the safe side with 3 mirrors and every rebuild wears 
> out the remaining drives, 1 out of the 3 would be enough since they hold 
> identical data
> 
> /dev/sdd: GB Written: 94.134
> 
> pretty impossible that both sides of the same mirror will fail within a 
> few hours
> 
You clearly have no clue why London Buses arrive in threes ... :-)

Cheers,
Wol

  reply	other threads:[~2022-09-11 18:34 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 [this message]
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

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=2bcebfce-6def-38f8-99be-1f5702905f94@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=h.reindl@thelounge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox