From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <okozina@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 25 Feb 2016 18:26:00 +0100 (CET)
References: <20160225160849.21765320@othir.localdomain>
 <56CF2938.2010102@redhat.com>
From: Ondrej Kozina <okozina@redhat.com>
Message-ID: <56CF3925.5060504@redhat.com>
Date: Thu, 25 Feb 2016 18:25:57 +0100
MIME-Version: 1.0
In-Reply-To: <56CF2938.2010102@redhat.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] help
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: Felix Wagner <felix@wagner-felix.com>, dm-crypt@saout.de

Hi again,

so I'm afraid you've actually found quite ugly bug in 
cryptsetup-reencrypt utility. Nevertheless there's still hope for your 
data because I believe the utility haven't overwritten any data. Keep 
reading.

I tried to reproduce the behaviour you've experienced:

Whenever I run cryptsetup-reencrypt and try to reference the luks device 
by /dev/disk/by-uuid symlink the utility fails. What is worse is fact 
that after this kind of failure (which is first bug) it removed the log 
file and header backup after it marked "dirty" the luks header on your 
drive (which much worse)!

I'll take care of these bugs, please follow the steps Milan sent on the 
list to recover your header. In fact it's not deleted only dirtied by 
the reencrypt utility.

Regards
O.