From: Reindl Harald <h.reindl@thelounge.net>
To: 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 14:20:54 +0200 [thread overview]
Message-ID: <dcef59a2-b8f6-ef8b-2fd6-2c8bfdfba4ad@thelounge.net> (raw)
In-Reply-To: <CAJH6TXi=pCvV2xcyWcOD4KVDP6BcoPdgdMqhSwyW9BMVEhtzYA@mail.gmail.com>
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
>> 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
----------------------
the only thing one should think of: are all 3 drives identical types
with identical age - then it's more likely that they fail all within a
short time
that's why i try to mix different disks in a mirror to avoid failing
both sides of a mirror due firmware-error or a charge of bad disks
----------------------
as i replaced my HDD to SSD i removed two drives out of my RAID10, as it
didn't boot exchange two of them
so at that point 1 mirror of each stripe was a HDD and one a new SSD,
after one year i replaced the remaining two disks
2 x 850 EVO 2TB
2 x 860 EVO 2TB
/dev/sda: GB Written: 72.020
/dev/sdb: GB Written: 69.709
/dev/sdc: GB Written: 91.367
/dev/sdd: GB Written: 94.134
pretty impossible that both sides of the same mirror will fail within a
few hours
next prev parent reply other threads:[~2022-09-11 12:21 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 [this message]
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
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=dcef59a2-b8f6-ef8b-2fd6-2c8bfdfba4ad@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=gandalf.corvotempesta@gmail.com \
--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