From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 2 Aug 2018 15:05:48 +0200 (CEST) References: <6df9d673-5392-1171-3cd7-ed8a244b565e@linux.ibm.com> <20180802092832.GA16707@h-174-65.A328.priv.bahnhof.se> <91ba1df1-0882-b843-c5e3-d4384e4ad08a@linux.ibm.com> From: Ondrej Kozina Message-ID: Date: Thu, 2 Aug 2018 15:05:46 +0200 MIME-Version: 1.0 In-Reply-To: <91ba1df1-0882-b843-c5e3-d4384e4ad08a@linux.ibm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-MW Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ingo Franzki , dm-crypt@saout.de On 08/02/2018 12:38 PM, Ingo Franzki wrote: > A better error message is fine, but I would rather like to see a fix that makes cryptsetup-reencrypt work with non-default LUKS2 header sizes This commit in wip-luks2 branch should fix it 1f36e33a. I need to add some tests yet, but hope this is it. Provided it passes tests I think this may get in 2.0.4 since it's one-liner. Regards O.