From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com
 [IPv6:2a00:1450:4013:c00::22b])
 (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, 14 Mar 2014 18:20:05 +0100 (CET)
Received: by mail-ee0-f43.google.com with SMTP id e53so1644706eek.30
 for <dm-crypt@saout.de>; Fri, 14 Mar 2014 10:20:05 -0700 (PDT)
Message-ID: <53233A43.3000705@gmail.com>
Date: Fri, 14 Mar 2014 18:20:03 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <loom.20140312T000413-75@post.gmane.org>
 <loom.20140314T085159-184@post.gmane.org> <20140314132256.GA31187@tansi.org>
 <loom.20140314T174259-734@post.gmane.org>
In-Reply-To: <loom.20140314T174259-734@post.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] cryptsetup-reencode: LUKS-${UUID}.new is too small
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: PePa <peter@passchier.net>, dm-crypt@saout.de

On 03/14/2014 05:46 PM, PePa wrote:
> Arno Wagner <arno@...> writes:
>>
>> The IO error is worrying though, it should _not_ happen.
>> Have a look into the system error log to see if this is 
>> some lower-level error.
>>
>> Arno
> 
> By the way, the log/new/org files stayed the same sizes througout the almost
> 10 hours of running: 512/5242880/527848 bytes.

Hi,

it is not updated until program is interrupted or you use --write-log.

Anyway, IO error is exactly the situation which cannot be handled correctly..

In theory, if you stop it with ctrl+c and then restart, it should try to continue
(log is updated in this case).

But first - what is in syslog? Is it really device error?

What version are you using? There were some fixes recently for 4k devices but
this really shout not happen in 99.4 % of device.

Please save files (log and two other) you cannot recover anything without them.
(If it really reencrypted 99% of device chances are that it can be manually fixed still.)

Please can you send me exact commands you run + device size of the device
(blockdev --getz <device>) and luksDump of your original image?
(either from temporary files or just send the whole temp. files with header)

It could be bug in reecryption so I would like to test it here.

Thanks,
Milan