From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 wQYB5f2jHZzQ for ; Sun, 30 Dec 2012 10:05:31 +0100 (CET) Received: from mail-ee0-f46.google.com (mail-ee0-f46.google.com [74.125.83.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sun, 30 Dec 2012 10:05:31 +0100 (CET) Received: by mail-ee0-f46.google.com with SMTP id e53so5696219eek.19 for ; Sun, 30 Dec 2012 01:05:30 -0800 (PST) Message-ID: <50E003D8.4030500@gmail.com> Date: Sun, 30 Dec 2012 10:05:28 +0100 From: Milan Broz MIME-Version: 1.0 References: <50DF72CE.3060801@gmail.com> <50DF7F1F.1020007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] (no subject) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ".. ink .." Cc: dm-crypt@saout.de On 12/30/2012 08:12 AM, .. ink .. wrote: > > As the above two commands show with "status" argument,the command fail when the given path is full path. Hm, because full path was never supported in fact as parameter (in API, cmdline should support it) (it should be the same identifies as you see in dmsetup). 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). Thanks, Milan