From: Sven Eschenberg <sven@whgl.uni-frankfurt.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Alignment issue with 4K disk
Date: Mon, 4 Jan 2016 22:54:52 +0100 [thread overview]
Message-ID: <568AEA2C.6010809@whgl.uni-frankfurt.de> (raw)
In-Reply-To: <1451943067.3914.4.camel@debian.org>
Hi,
start=4194304 -> assumind this is in 512 byte blocks, the start sector
is aligned to MByte boundary and thus 4k boundary.
Anyway, if your device only has one partition which is encrypted with
dm-crypt, set it up to start at sector 2048 (which should be default for
parted, fdisk and so on). Pass align-payload 2048 during creation of the
LUKS header, which will give you an MByte boundary and should always be
okay.
If the kernel still complains, then something else might be going wrong.
Regards
-Sven
Am 04.01.2016 um 22:31 schrieb Yves-Alexis Perez:
> Hi,
>
> I'm trying to setup an encrypted volume on an external disk which has 4k
> physical sector size (with 512b logical sector size).
>
> I've used various parted option (-a none / minimal / optimal) and various --
> align-payload options to cryptsetup, but everytime I luksOpen the container, I
> get a kernel log with:
>
> janv. 04 22:25:04 scapa kernel: device-mapper: table: 253:4: adding target device sdb1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=4194304
>
> (argument for start= changes for different values of the --align-payload)
>
> I'm not sure it's really serious, but any idea how to fix that?
>
> Regards,
>
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
next prev parent reply other threads:[~2016-01-04 21:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 21:31 [dm-crypt] Alignment issue with 4K disk Yves-Alexis Perez
2016-01-04 21:54 ` Sven Eschenberg [this message]
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
2016-01-10 0:25 Eugen Rogoza
2016-01-10 1:14 ` Sven Eschenberg
2016-01-10 4:30 ` Sven Eschenberg
2016-01-10 15:18 Eugen Rogoza
2016-01-10 15:37 Eugen Rogoza
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
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=568AEA2C.6010809@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.