From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhogomchungu@gmail.com>
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com
 [IPv6:2607:f8b0:400d:c04::22c])
 (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>; Thu,  7 Jan 2016 19:01:03 +0100 (CET)
Received: by mail-qg0-x22c.google.com with SMTP id e32so243681926qgf.3
 for <dm-crypt@saout.de>; Thu, 07 Jan 2016 10:01:03 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <1451988842.3914.18.camel@debian.org>
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>
From: ".. ink .." <mhogomchungu@gmail.com>
Date: Thu, 7 Jan 2016 21:00:41 +0300
Message-ID: <CAFnMBaQLwTbFeeVJn-XR2eKRLy4jJb8-hFrrm02AzoGqkEOFTw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
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: "dm-crypt@saout.de" <dm-crypt@saout.de>

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

On Tue, Jan 5, 2016 at 1:14 PM, Yves-Alexis Perez <corsac@debian.org> wrote:
> On mar., 2016-01-05 at 00:02 +0100, Sven Eschenberg wrote:
>> Hi Alexis,
>
> (Yves-Alexis actually)
>>
>> I stumbled over this line:
>>
>> I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
>>
>> The latter resembles 65535 sectors (512 Byte logical ones), which
>> explains why the automated alignment was done at sector 65535. This
>> value seems extremely weird though.
>>
>> You said the drive was external, connected how? USB maybe?
>
> Yes. It's a Samsung T3 disk, so everything is integrated (disk+sata/usb3
> adapter), not much chance I can do anything here.
>
> I'll try to force the alignment to 2048s for part1 and see what happens.
>>
>> Can you take a look at hdparm -I /dev/sdc? Anything unusual there?
>
> I'll try tonight (I don't have it at hand).
>
> Thanks for the pointers though.
> --
> Yves-Alexis
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>