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 hVyzT0F9Xy35 for <dm-crypt@saout.de>;
 Fri,  8 Nov 2013 12:08:05 +0100 (CET)
Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com
 [IPv6:2a00:1450:4008:c01::22c])
 (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>; Fri,  8 Nov 2013 12:08:05 +0100 (CET)
Received: by mail-bk0-f44.google.com with SMTP id mx11so682559bkb.17
 for <dm-crypt@saout.de>; Fri, 08 Nov 2013 03:08:04 -0800 (PST)
Message-ID: <527CC60A.6060503@gmail.com>
Date: Fri, 08 Nov 2013 12:07:54 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <1936143146.13978602.1383905882759.JavaMail.root@redhat.com>
In-Reply-To: <1936143146.13978602.1383905882759.JavaMail.root@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] run cryptsetup-reencrypt failed
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: Xiao Ni <xni@redhat.com>, dm-crypt@saout.de
Cc: Ondrej Kozina <okozina@redhat.com>


On 8.11.2013 11:18, Xiao Ni wrote:
>     [root@storageqe-06 /]# ./cryptsetup-1.6.2/src/cryptsetup-reencrypt /dev/dm-10  --debug

First, NEVER EVER use /dec/dm-X devices directly.
Always use symbolic links in /dev/mapper or other links, which are not dynamic.

...
> open device LUKS-bfeb35f1-90b9-4bc6-ba43-a4302db7957b.new
> path is LUKS-bfeb35f1-90b9-4bc6-ba43-a4302db7957b.new
> file path is (null)

this is strange.

It creates temporary LUKS headers in file in current directory.
What filesystem you are using there?


> open device LUKS-bfeb35f1-90b9-4bc6-ba43-a4302db7957b.new             //I thinks it should open /dev/loop0
> path is /dev/loop0

no, loop should be hidden there.

Anyway, could you add this to issues http://code.google.com/p/cryptsetup/issues/list
and add more info about your system?

I know you are using some complex storage config like multipath, so the best way
will be to discuss it with Ondra (as my former RH colleague) inside RH and when you
have all the info, just report it to issues page.


Thanks,
Milan