From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com
 [IPv6:2a00:1450:400c:c09::242])
 (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>; Sun, 10 Apr 2016 10:10:45 +0200 (CEST)
Received: by mail-wm0-x242.google.com with SMTP id l6so14240725wml.3
 for <dm-crypt@saout.de>; Sun, 10 Apr 2016 01:10:45 -0700 (PDT)
References: <CABmFtOr==FCLB6Y_pmnko-y6-HMv4LxS_X6K+rp=H6WK-z1HMg@mail.gmail.com>
 <CABmFtOo6-Zq6aMQNKYKr7fmpsqVpS7h7z8YCpbAhdcMdq8iMRg@mail.gmail.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <570A0A82.4050105@gmail.com>
Date: Sun, 10 Apr 2016 10:10:42 +0200
MIME-Version: 1.0
In-Reply-To: <CABmFtOo6-Zq6aMQNKYKr7fmpsqVpS7h7z8YCpbAhdcMdq8iMRg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] LUKS1 devmapper device mount issue
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: Amith Kumar Ramachandra <amitnr@gmail.com>, dm-crypt@saout.de

On 04/10/2016 07:15 AM, Amith Kumar Ramachandra wrote:

> I dumped ldd dmsetup and I see dmsetup uses almost the same set and
> version of libraries cryptsetup uses. seems a mystery dmsetup created
> devmapper device on formatting mounts fine but not crypsetup created
> .....

Hi,

I would say you are hitting some kernel problem here.

Please can you try

 - use new cryptsetup versision (1.7.1)

 - if dmestup works, please show the exact difference in mapping table.
(My guess it is only in offset reserved for header - you will need to decrease
device size as well. We are probably hitting some kernel bug when start of crypt
device is not aligned to mmc block.)

Could you try to create exact mapping table as LUKS does?
(Just activate LUKS using cryptsetup, check dmsetup table --showkeys
and repeat it with dmsetup.)
If you still see the problem, then kernel is the source of problem.

Anyway, there were a lot of changes related to aarch64, so if
you can use more recent kernel, it would be nice as well.
(According to log you are using Linux 3.18.21-tegra aarch64.)

Milan