All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eschenberg <sven@whgl.uni-frankfurt.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Alignment issue with 4K disk
Date: Sun, 10 Jan 2016 02:14:02 +0100	[thread overview]
Message-ID: <5691B05A.3040504@whgl.uni-frankfurt.de> (raw)
In-Reply-To: <trinity-5a6d1acc-8969-431b-9aee-fa936367ea26-1452385519461@3capp-gmx-bs36>

Hi Eugen,

Indeed the optimal IO value (on sdc) seems a little weird. Yet this 
should not create any alignment warnings.

zuluCrypt-1001-NAAN-sdc4-1790378342: 0 11406264975 - Now this is not 4k 
aligned (sectors must be divideable by 8 to be 4k aligned). Indeed the 
encrypted payload should start at 11406264976 sectors, so there is a -1 
sector misalignment (See lsblk output saying so). VeraCrypt did not 
properly align the payload when the container was created, I assume.

Regards

-Sven


Am 10.01.2016 um 01:25 schrieb Eugen Rogoza:
> Hi,
>
>> Reporter should paste output of "lsblk -t" with device activated to check what underlying
>> device report alignment limits are violated in storage stack).
>
> I am the reporter and the output of 'lsblk -t' with encrypted partition mounted is below. sda2 is the one that works fine, sdc4 is the one that throws alignment warnings.
>
> root@nuc:~> lsblk -t
> NAME                                    ALIGNMENT MIN-IO   OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE  RA WSAME
> sda                                             0   4096        0    4096     512    1 cfq       128 128    0B
> ├─sda1                                          0   4096        0    4096     512    1 cfq       128 128    0B
> └─sda2                                          0   4096        0    4096     512    1 cfq       128 128    0B
>    └─zuluCrypt-1001-NAAN-sda2-4071757814         0   4096        0    4096     512    1           128 128    0B
> sdb                                             0    512        0     512     512    0 noop      128 128    0B
> ├─sdb1                                          0    512        0     512     512    0 noop      128 128    0B
> ├─sdb2                                          0    512        0     512     512    0 noop      128 128    0B
> ├─sdb3                                          0    512        0     512     512    0 noop      128 128    0B
> └─sdb4                                          0    512        0     512     512    0 noop      128 128    0B
> sdc                                             0   4096 33553920    4096     512    1 cfq       128 128   32M
> ├─sdc1                                          0   4096 33553920    4096     512    1 cfq       128 128   32M
> ├─sdc2                                          0   4096 33553920    4096     512    1 cfq       128 128   32M
> ├─sdc3                                          0   4096 33553920    4096     512    1 cfq       128 128   32M
> └─sdc4                                          0   4096 33553920    4096     512    1 cfq       128 128   32M
>    └─zuluCrypt-1001-NAAN-sdc4-1790378342        -1   4096        0    4096     512    1           128 128    0B
>
>
>
>> That is indeed true and further info including 'dmsetup table' will be
>> necessary to tell what is really going on.
>
> Output below. Again, sdc4 is the problematic one.
>
> root@nuc:~> dmsetup table
> zuluCrypt-1001-NAAN-sdc4-1790378342: 0 11406264975 crypt aes-xts-plain64 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 256 8:36 256
> zuluCrypt-1001-NAAN-sda2-4071757814: 0 1324371456 crypt aes-xts-plain64 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 256 8:2 256
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>

  reply	other threads:[~2016-01-10  1:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10  0:25 [dm-crypt] Alignment issue with 4K disk Eugen Rogoza
2016-01-10  1:14 ` Sven Eschenberg [this message]
2016-01-10  4:30   ` Sven Eschenberg
  -- strict thread matches above, loose matches on Subject: below --
2016-01-10 17:22 Eugen Rogoza
2016-01-10 19:13 ` Sven Eschenberg
2016-01-10 20:20   ` Eugen Rogoza
2016-01-10 21:00     ` Sven Eschenberg
2016-01-10 15:37 Eugen Rogoza
2016-01-10 15:18 Eugen Rogoza
2016-01-04 21:31 Yves-Alexis Perez
2016-01-04 21:54 ` Sven Eschenberg
2016-01-04 22:20   ` Yves-Alexis Perez
2016-01-04 22:41     ` Sven Eschenberg
2016-01-04 23:02     ` Sven Eschenberg
2016-01-05 10:14       ` Yves-Alexis Perez
2016-01-07 18:00         ` .. ink ..
2016-01-09 12:30           ` Milan Broz
2016-01-09 14:47             ` Sven Eschenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5691B05A.3040504@whgl.uni-frankfurt.de \
    --to=sven@whgl.uni-frankfurt.de \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.