From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com
 [IPv6:2a00:1450:400c:c09::22a])
 (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>; Tue, 12 Apr 2016 14:20:51 +0200 (CEST)
Received: by mail-wm0-x22a.google.com with SMTP id f198so185155317wme.0
 for <dm-crypt@saout.de>; Tue, 12 Apr 2016 05:20:51 -0700 (PDT)
References: <CABmFtOr==FCLB6Y_pmnko-y6-HMv4LxS_X6K+rp=H6WK-z1HMg@mail.gmail.com>
 <CABmFtOo6-Zq6aMQNKYKr7fmpsqVpS7h7z8YCpbAhdcMdq8iMRg@mail.gmail.com>
 <570A0A82.4050105@gmail.com>
 <CABmFtOoEbZMDbnEYiT5DWeGeXv8jGBrE-0zuMKP6GcuwRNaa9w@mail.gmail.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <570CE81F.2000706@gmail.com>
Date: Tue, 12 Apr 2016 14:20:47 +0200
MIME-Version: 1.0
In-Reply-To: <CABmFtOoEbZMDbnEYiT5DWeGeXv8jGBrE-0zuMKP6GcuwRNaa9w@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>
Cc: dm-crypt@saout.de

On 04/10/2016 11:04 PM, Amith Kumar Ramachandra wrote:
...
> You can see the table does match the cryptsetup one...
> 
> #mke2fs /devmapper/data #mount /dev/mapper/data /mnt #mount .... 
> .... /dev/mapper/data on /mnt type ext2 (rw,relatime) And device is
> mounted.

This is really strange (cryptsetup is basically just calling the same dm-ioctl in the end),
> 
>>> use new cryptsetup versision (1.7.1)
> I could switch and check I suppose. But here is one more data point
> ...
> 
> My environment where I run into issue with cryptsetup is on /Yocto
> root file system, /an embedded distribution of Linux. However, when I
> switch to Ubuntu 15.04 RFS(which is an alternate version I also boot
> sometimes) with the same linux kernel, cryptsetup binary and
> libcryptsetup.so as Yocto, the cryptsetup devmapper device mounts
> fine. I then started narrowing down the differences b/w yocto and
> ubuntu in terms of libraries etc... then I found that if I use the
> /systemd /executable in /usr/lib/system/systemd from Ubuntu RFS in
> the Yocto, all yocto mount problems go away. (not sure what systemd
> has got to do with cryptsetup and mount)
> 
> If you are still with me, does this tell you anything at all? :)

Looks like a magic :)
Really, no idea - systemd should just process /etc/crypttab devices.
It can be something stupid but without local reproducer it is hard to say...
If it is systemd, checking its log could help here.

Milan