From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] btrfs conversion: first impressions
Date: Wed, 14 May 2014 01:09:17 +0200 [thread overview]
Message-ID: <5372A61D.9060406@xunil.at> (raw)
In-Reply-To: <20140514000228.546a90f2@hactar.digimed.co.uk>
Am 14.05.2014 01:02, schrieb Neil Bothwick:
> On Wed, 14 May 2014 00:34:12 +0200, Stefan G. Weichinger wrote:
>
>> How to transform partitions/directories set up with cryptsetup
>> into this new world? Set up a btrfs on top of the crypted fs ? I
>> ask because I look for a clean setup for my 2 thinkpads.
>
> Encrypt the partition(s) with cryptsetup and them use the devices
> in /dev/mapper to create the volumes. That's how I have my ZFS
> pools set up and I'm looking to do the same when I try BTRFS.
Doesn't that screw up the whole idea of checksumming etc ?
In my understanding the FS (=btrfs or zfs) should have the direct
contact to the "metal" (=hdd/sdd) to be fully able to detect bitrot
and stuff.
btrfs inside a crypted volume will work, yes, but it won't be able to
see or correct flipping bits on the hardware, because the underlying
layers of cryptsetup etc might hide them.
Right?
next prev parent reply other threads:[~2014-05-13 23:09 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 [this message]
2014-05-14 0:39 ` Neil Bothwick
2014-05-14 8:01 ` Stefan G. Weichinger
2014-05-14 8:42 ` Neil Bothwick
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=5372A61D.9060406@xunil.at \
--to=lists@xunil.at \
--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