From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com
 [IPv6:2a00:1450:400c:c09::230])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sat,  9 Jan 2016 13:30:40 +0100 (CET)
Received: by mail-wm0-x230.google.com with SMTP id l65so162774074wmf.1
 for <dm-crypt@saout.de>; Sat, 09 Jan 2016 04:30:39 -0800 (PST)
References: <1451943067.3914.4.camel@debian.org>
 <568AEA2C.6010809@whgl.uni-frankfurt.de>
 <1451946046.3914.13.camel@debian.org>
 <568AFA13.2010208@whgl.uni-frankfurt.de>
 <1451988842.3914.18.camel@debian.org>
 <CAFnMBaQLwTbFeeVJn-XR2eKRLy4jJb8-hFrrm02AzoGqkEOFTw@mail.gmail.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <5690FD6D.4050605@gmail.com>
Date: Sat, 9 Jan 2016 13:30:37 +0100
MIME-Version: 1.0
In-Reply-To: <CAFnMBaQLwTbFeeVJn-XR2eKRLy4jJb8-hFrrm02AzoGqkEOFTw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Alignment issue with 4K disk
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: ".. ink .." <mhogomchungu@gmail.com>, "dm-crypt@saout.de" <dm-crypt@saout.de>



On 01/07/2016 07:00 PM, .. ink .. wrote:
> There is another (i think) related problem that was reported here[1]
> 
> Are these warnings serious or can they be ignored?
> 
> 
> [1] https://github.com/mhogomchungu/zuluCrypt/issues/25

If I read this correctly, it s caused by mapping of an unaligned plaintext device-mapper
device (unlocked VeraCrypt) to underlying partition.

That's a bug (or lack of proper alignment) inside VeraCrypt header or in GPT partitioning
- it should respect underlying device alignment while creating device/partition.

Anyway, I think the only consequence should be performance drop, it should still work.

Note that output from GPT says 512B while dm kernel message says 4k block... GPT should
use 4k block as well.
Reporter should paste output of "lsblk -t" with device activated to check what underlying
device report alignment limits are violated in storage stack).

We cannot do anything with it I guess, cryptsetup just activates what is written inside
Veracrypt header using alignment limits reported by kernel.

Milan