DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Amith Kumar Ramachandra <amitnr@gmail.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS1 devmapper device mount issue
Date: Sun, 10 Apr 2016 10:10:42 +0200	[thread overview]
Message-ID: <570A0A82.4050105@gmail.com> (raw)
In-Reply-To: <CABmFtOo6-Zq6aMQNKYKr7fmpsqVpS7h7z8YCpbAhdcMdq8iMRg@mail.gmail.com>

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

  reply	other threads:[~2016-04-10  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 20:46 [dm-crypt] LUKS1 devmapper device mount issue Amith Kumar Ramachandra
2016-04-09 12:36 ` Michael Kjörling
2016-04-10  5:15 ` Amith Kumar Ramachandra
2016-04-10  8:10   ` Milan Broz [this message]
2016-04-10 21:04     ` Amith Kumar Ramachandra
2016-04-12 12:20       ` Milan Broz

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=570A0A82.4050105@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=amitnr@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