From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com
 [IPv6:2a00:1450:400c:c09::22d])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 25 Feb 2016 18:55:55 +0100 (CET)
Received: by mail-wm0-x22d.google.com with SMTP id g62so40459736wme.1
 for <dm-crypt@saout.de>; Thu, 25 Feb 2016 09:55:55 -0800 (PST)
References: <20160225160849.21765320@othir.localdomain>
 <56CF2DC2.6050008@gmail.com> <20160225180518.49410783@othir.localdomain>
 <56CF37F7.5060501@gmail.com> <20160225184939.2644e098@othir.localdomain>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <56CF4028.4000906@gmail.com>
Date: Thu, 25 Feb 2016 18:55:52 +0100
MIME-Version: 1.0
In-Reply-To: <20160225184939.2644e098@othir.localdomain>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] help
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: Felix Wagner <felix@wagner-felix.com>
Cc: Ondrej Kozina <okozina@redhat.com>, dm-crypt@saout.de

On 02/25/2016 06:49 PM, Felix Wagner wrote:
> I do have one more question. I recently updated my arch system and now
> whenever I luksOpen the mapped dev gets mounted automatically. Is this
> arch specific or cryptsetup?

cryptsetup never mounts any filesystem itself, so it is question
for Arch distro experts (I guess it is some crypttab/fstab/systemd magic).


Just adition to reencryption bug - the problem is to use dynamic path in /dev/
that uses UUID. This path/UUID disappears once reencrypt utility marks device
non-LUKS (temporarily, in the middle of operation).

(The real bug is that reencrypt utility fails to recover properly in this situation,
this path just cannot be used.)

So just using proper device (like /dev/sdb or so) and it should work.

Milan