From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Encrypted Raid 1 Btrfs on *Single Drive*
Date: Sat, 15 Mar 2014 07:07:30 -0400 [thread overview]
Message-ID: <53243472.7000108@gmail.com> (raw)
In-Reply-To: <CAFnMBaSuLCZYJVAaSP7DZ4JtDUuTNaJp-V0kJL7=J03_kvo1bQ@mail.gmail.com>
On 03/14/2014 08:00 AM, .. ink .. wrote:
> I think somehow,the kpartx step was done here and this is evident by the
> existence of /dev/mapper/vault1 & vault2
Hi,
No, I didn't run kpartx at this step. I did run "partprobe" after fdisk
here in Fedora 20. Maybe one of them creates the partition device files.
> I think here,you should have done:
> kpartx -d /dev/mapper/vault
> cryptsetup luksClose vault
There you go. Thanks for this. That worked nicely. I'll add this to my
steps.
> The "standard way" is to create an LVM volume in the encrypted
> container.This is how most distributions implements "full disk
> encryption" with LUKS.
>
> With an LVM volume,you can simulate partitions by creating volume
> groups/logical volumes.
In my scenario, running btrfs over LVM seems overkill since BTRFS has
already built-in volume management.
Thanks!
Jorge
prev parent reply other threads:[~2014-03-15 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 11:09 [dm-crypt] Encrypted Raid 1 Btrfs on *Single Drive* Jorge Fábregas
2014-03-14 12:00 ` .. ink ..
2014-03-15 11:07 ` Jorge Fábregas [this message]
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=53243472.7000108@gmail.com \
--to=jorge.fabregas@gmail.com \
--cc=dm-crypt@saout.de \
/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