From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] btrfs conversion: first impressions
Date: Wed, 14 May 2014 09:42:47 +0100 [thread overview]
Message-ID: <20140514094247.7753ea59@digimed.co.uk> (raw)
In-Reply-To: <537322E6.9040907@xunil.at>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Wed, 14 May 2014 10:01:42 +0200, Stefan G. Weichinger wrote:
> >> Doesn't that screw up the whole idea of checksumming etc ?
> >
> > Not to my mind. The bits are recorded and checksummed, that's what
> > matters. If a bit on a platter is flipped, the decrypted bits will
> > also change.
>
> But then the "container" of the btrfs would be corrupted, right?
No, because each element of the RAID is encrypted separately, so btrfs
can still use the good one to repair the bad one. If you were to create
an mdadm array, put dm-crypt on that and then btrfs on top, which is more
efficient because it encrypts each byte only once, then you would lose
the check and repair facilities.
--
Neil Bothwick
-Come, come, why they couldn't hit an elephant from this dist-
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-05-14 8:43 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:18 [gentoo-user] planned btrfs conversion: questions Marc Joliet
2014-05-06 18:13 ` [gentoo-user] " James
2014-05-06 23:30 ` Marc Joliet
2014-05-06 22:53 ` [gentoo-user] " Marc Joliet
2014-05-07 15:12 ` Marc Joliet
2014-05-09 21:05 ` Marc Joliet
2014-05-06 22:56 ` William Kenworthy
2014-05-06 23:51 ` Marc Joliet
2014-05-08 11:57 ` William Kenworthy
2014-05-08 18:14 ` Stefan G. Weichinger
2014-05-09 19:59 ` Stefan G. Weichinger
2014-05-10 11:14 ` Stefan G. Weichinger
2014-05-11 12:35 ` Stefan G. Weichinger
2014-05-11 16:17 ` Stefan G. Weichinger
2014-05-11 17:37 ` Peter Humphrey
2014-05-11 21:24 ` [gentoo-user] btrfs conversion: first impressions Stefan G. Weichinger
2014-05-12 14:30 ` Marc Joliet
2014-05-12 18:28 ` Stefan G. Weichinger
2014-05-13 22:34 ` Stefan G. Weichinger
2014-05-13 23:02 ` Neil Bothwick
2014-05-13 23:09 ` Stefan G. Weichinger
2014-05-14 0:39 ` Neil Bothwick
2014-05-14 8:01 ` Stefan G. Weichinger
2014-05-14 8:42 ` Neil Bothwick [this message]
2014-05-14 8:54 ` Stefan G. Weichinger
2014-05-14 9:26 ` Neil Bothwick
2014-05-14 9:30 ` Stefan G. Weichinger
2014-05-15 6:17 ` Stefan G. Weichinger
2014-05-12 11:19 ` [gentoo-user] planned btrfs conversion: questions Stefan G. Weichinger
2014-05-08 20:43 ` Marc Joliet
2014-05-10 9:33 ` William Kenworthy
2014-05-11 8:53 ` Mick
2014-05-11 10:43 ` William Kenworthy
2014-05-11 12:29 ` Peter Humphrey
2014-05-11 15:53 ` Alan McKinnon
2014-05-12 14:08 ` Marc Joliet
2014-05-12 14:39 ` Peter Humphrey
2014-05-12 15:04 ` Marc Joliet
2014-05-12 16:15 ` Dale
2014-05-12 19:12 ` Marc Joliet
2014-05-12 19:28 ` Daniel Frey
2014-05-07 2:33 ` [gentoo-user] " Jonathan Callen
2014-05-16 20:15 ` [gentoo-user] experience thus far (was: planned btrfs conversion: questions) Marc Joliet
2014-05-16 20:43 ` Marc Joliet
2014-05-17 0:08 ` [gentoo-user] experience thus far William Kenworthy
2014-05-17 0:44 ` Marc Joliet
2014-05-17 3:02 ` William Kenworthy
2014-05-17 7:53 ` Mick
2014-05-17 11:41 ` Rich Freeman
2014-05-17 10:07 ` Neil Bothwick
2014-05-17 12:35 ` William Kenworthy
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=20140514094247.7753ea59@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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