From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jorge.fabregas@gmail.com>
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com
 [IPv6:2607:f8b0:4002:c07::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sat, 15 Mar 2014 12:07:32 +0100 (CET)
Received: by mail-yk0-f173.google.com with SMTP id 10so9683365ykt.4
 for <dm-crypt@saout.de>; Sat, 15 Mar 2014 04:07:30 -0700 (PDT)
Received: from biodora.local ([70.45.26.78])
 by mx.google.com with ESMTPSA id n21sm22012817yhm.1.2014.03.15.04.07.30
 for <dm-crypt@saout.de>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Sat, 15 Mar 2014 04:07:30 -0700 (PDT)
Message-ID: <53243472.7000108@gmail.com>
Date: Sat, 15 Mar 2014 07:07:30 -0400
From: =?ISO-8859-1?Q?Jorge_F=E1bregas?= <jorge.fabregas@gmail.com>
MIME-Version: 1.0
References: <5322E353.9090602@gmail.com>
 <CAFnMBaSuLCZYJVAaSP7DZ4JtDUuTNaJp-V0kJL7=J03_kvo1bQ@mail.gmail.com>
In-Reply-To: <CAFnMBaSuLCZYJVAaSP7DZ4JtDUuTNaJp-V0kJL7=J03_kvo1bQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Encrypted Raid 1 Btrfs on *Single Drive*
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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