From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aDF-xWcdvOaA for ; Fri, 7 Dec 2012 04:58:55 +0100 (CET) Received: from mail-ia0-f174.google.com (mail-ia0-f174.google.com [209.85.210.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 7 Dec 2012 04:58:54 +0100 (CET) Received: by mail-ia0-f174.google.com with SMTP id y25so60707iay.5 for ; Thu, 06 Dec 2012 19:58:53 -0800 (PST) MIME-Version: 1.0 Date: Thu, 6 Dec 2012 19:58:52 -0800 Message-ID: From: Vadim Finkelstein Content-Type: multipart/alternative; boundary=f46d0401f591e061be04d03b3b30 Subject: [dm-crypt] 4k block size in dm-crypt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de --f46d0401f591e061be04d03b3b30 Content-Type: text/plain; charset=ISO-8859-1 Regarding this: http://www.saout.de/pipermail/dm-crypt/2011-April/001673.html Was the issue of 4k block sizes ever solved? I have applied a 4k block size patch to my dm-crypt, but now seeing the same problem - if the data is read back with block size of 8192 (for example) it does not match what was previously written with block size of 4092. --f46d0401f591e061be04d03b3b30 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Regarding this:

Was the issue of 4k block= sizes ever solved? I have applied a 4k block size patch to my dm-crypt, bu= t now seeing the same problem - if the data is read back with block size of= 8192 (for example) it does not match what was previously written with bloc= k size of 4092.=A0
--f46d0401f591e061be04d03b3b30-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mhai6_0xbmig for ; Fri, 7 Dec 2012 12:53:29 +0100 (CET) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 7 Dec 2012 12:53:29 +0100 (CET) Received: by mail-wi0-f180.google.com with SMTP id hj13so338911wib.1 for ; Fri, 07 Dec 2012 03:53:29 -0800 (PST) Message-ID: <50C1D8B4.3080503@gmail.com> Date: Fri, 07 Dec 2012 12:53:24 +0100 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] 4k block size in dm-crypt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vadim Finkelstein Cc: dm-crypt@saout.de On 12/07/2012 04:58 AM, Vadim Finkelstein wrote: > Regarding this: > http://www.saout.de/pipermail/dm-crypt/2011-April/001673.html > > Was the issue of 4k block sizes ever solved? I have applied a 4k > block size patch to my dm-crypt, but now seeing the same problem - if > the data is read back with block size of 8192 (for example) it does > not match what was previously written with block size of 4092. What issue? The patch is not upstream and cannot be used wihout additional changes. If we add block-size parameter, we must reject all unaligned and partial block reads to avoid this problem (and this part is still missing, set proper io hinds for device and announce proper block size). I would like to have such parameter one day in dmcrypt, but still not sure what's the real use case (except workaround slow hw accelerators). (And AES-NI and clones works quite well here with 512 block.) Milan