From: Reindl Harald <h.reindl@thelounge.net>
To: Roman Mamedov <rm@romanrm.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 11:40:43 +0200 [thread overview]
Message-ID: <e5aabf02-3735-b1eb-d349-e4f1c7bb9d18@thelounge.net> (raw)
In-Reply-To: <20220912142624.63ba4b5c@nvm>
Am 12.09.22 um 11:26 schrieb Roman Mamedov:
> 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.
better safe than sorry
in the past 15 years i replaced 6 drives on 8 machines (each 4 disks)
while some are running since 2011
on every location with machines i am resposible for is at least one
replacment disk, switch, order a new reserve disk, case closed
> 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
my backup scheme is perfect but my personal lifetime is much more worth
than a disk costs these days - the backups are regulary testet and in
the past 20 years i didn't need them which is a good thing
no backup on this planet contains the last 30 minutes of work besides
that outtakes typically happen in the moment where you have no time to
deal with such events
come on a restore a backup in a production environment, your customers
will be not much thankful when they lose the last 30 minutes of all
mails and work....
next prev parent reply other threads:[~2022-09-12 9:40 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 [this message]
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=e5aabf02-3735-b1eb-d349-e4f1c7bb9d18@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=antlists@youngman.org.uk \
--cc=gandalf.corvotempesta@gmail.com \
--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