From: Roman Mamedov <rm@romanrm.net>
To: Hans van Kranenburg <Hans.van.Kranenburg@mendix.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: dm-integrity + mdadm + btrfs = no journal?
Date: Wed, 30 Jan 2019 13:42:19 +0500 [thread overview]
Message-ID: <20190130134219.13a4b558@natsu> (raw)
In-Reply-To: <2a321782-d258-1ef3-8d25-149b8e24e819@mendix.com>
On Tue, 29 Jan 2019 23:15:18 +0000
Hans van Kranenburg <Hans.van.Kranenburg@mendix.com> wrote:
> So, what I was thinking of is:
>
> * Use dm-integrity on partitions on the individual disks
> * Use mdadm RAID10 on top (which is then able to repair bitrot)
> * Use LVM on top
> * Etc...
You never explicitly say what's the whole idea, what are you protecting
against. By mentions of bitrot and of dm-integrity, you seem to think that
when hardware is "starting to fall apart" the disks will eventually start
returning wrong/corrupt data.
Thing is, they do not. What you will get on disks going bad is uncorrectable
read errors (UNC), not a silent corruption. The latter is still possible, but
more likely to be caused by the SATA controller issues (or its
driver/firmware), not disks. And those are hardly related to whether it's
"new" or "old".
--
With respect,
Roman
next prev parent reply other threads:[~2019-01-30 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 23:15 dm-integrity + mdadm + btrfs = no journal? Hans van Kranenburg
2019-01-30 1:02 ` Chris Murphy
2019-01-30 8:42 ` Roman Mamedov [this message]
2019-01-30 12:58 ` Austin S. Hemmelgarn
2019-01-30 15:26 ` Christoph Anton Mitterer
2019-01-30 16:00 ` Austin S. Hemmelgarn
2019-01-30 16:31 ` Christoph Anton Mitterer
2019-01-30 16:38 ` Hans van Kranenburg
2019-01-30 16:56 ` Hans van Kranenburg
-- strict thread matches above, loose matches on Subject: below --
2018-11-04 22:55 Hans van Kranenburg
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=20190130134219.13a4b558@natsu \
--to=rm@romanrm.net \
--cc=Hans.van.Kranenburg@mendix.com \
--cc=linux-btrfs@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.