From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 4QTqbCdi_bss for <dm-crypt@saout.de>;
 Sun, 30 Dec 2012 11:51:28 +0100 (CET)
Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com
 [209.85.215.182])
 (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>; Sun, 30 Dec 2012 11:51:28 +0100 (CET)
Received: by mail-ea0-f182.google.com with SMTP id a14so4753100eaa.27
 for <dm-crypt@saout.de>; Sun, 30 Dec 2012 02:51:27 -0800 (PST)
Message-ID: <50E01CAD.4000900@gmail.com>
Date: Sun, 30 Dec 2012 11:51:25 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <CAFnMBaSrkvufXW=wAJDA-=ntZczvVnT+KUqe1ZSbe4inHAL2Tg@mail.gmail.com>
 <50DF72CE.3060801@gmail.com>
 <CAFnMBaR3S3nmYdvN4X=R4sbLJzE+3z3pZXgRLRE_xd+mmCC_QA@mail.gmail.com>
 <50DF7F1F.1020007@gmail.com>
 <CAFnMBaS2_0XW0DyFDEcTgHiU-42PmmjC_CPiko-1NoTttcrQpw@mail.gmail.com>
 <50E003D8.4030500@gmail.com>
 <CAFnMBaSm8xBy+AWw0PWETeBqO0S5w0wWOXmp0Cefa6KOwBVXcw@mail.gmail.com>
In-Reply-To: <CAFnMBaSm8xBy+AWw0PWETeBqO0S5w0wWOXmp0Cefa6KOwBVXcw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] (no subject)
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: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de

On 12/30/2012 10:19 AM, .. ink .. wrote:
> Device-mapper programs usually strip path if it is default
> /dev/mapper though. Anyway, I'll check what can be done here (mainly
> if it worked before).
> 
> 
> It always worked with full path,In my test here,full path still works
> with plain volumes as well as luks volumes.Only truecrypt volumes
> have a problem and this suggests code paths specific to truecrypt
> volumes are at fault.

Seems it was combination of not-too-much compatible change in libdevmapper
(it stat() the path and fails earlier) and combination of new features in tcrypt.

Should be fixed in git tree now.

Thanks,
Milan