From: Ondrej Kozina <okozina@redhat.com>
To: dm-devel@redhat.com
Cc: laurent cop <laurent.cop@gmail.com>
Subject: Re: LUKS2 - RAID0 - NVME : alignment issue
Date: Fri, 12 Oct 2018 18:09:24 +0200 [thread overview]
Message-ID: <e93e5cdb-10be-8bec-b33b-150bad9a32ac@redhat.com> (raw)
In-Reply-To: <CAHzw6onNd8JskiB75PzFd4Zo45dP4fx3emoHFz8eTNkTV2+7+A@mail.gmail.com>
On 10/12/2018 01:56 PM, laurent cop wrote:
> Hello,
>
> I have trouble while in top of the stack :
> mkfs.ext4 /dev/mapper/raid0luks2
> /dev/mapper/raid0luks2 alignement is offset by 147456 bytes
> This may result in very poor performance (re-) partitioning is suggested.
> I have the same pb with mkfs.xfs
>
> I am using following scheme:
>
> LUKS2 => created with cryptsetup -v luksFormat --type luks2
> /dev/md127 --cipher aes-gcm-random --integrity aeae
There's a bug in align offset calculations in cryptsetup for LUKS2
format. It'll get fixed with future 2.0.5 release.
Provided you don't have real data on the LUKS2 device already...could
you provide us with --debug output from the luksFormat action run again?
It'd help me to find out if it gets fixed with commit dd36d56d472e.
Regards
O.
> RAID 0 => created with mdadm chunk=32
> 3 Disks *NVME* => partition with gdisk (fist sector : 2048)
>
> I got this information with lsblk -t for each 3 disks, i got the same
> information.
> nvmeXn1
> -> NvmeXn1p1 ALIGN = 0
> -> md127 ALIGN = 0
> -> raid0luks2_dif ALIGN = 147456
> -> raid0luks2 ALIGN = 147456
> 1) How can I solve my alignment issue?
> 2) Is it normal to have low performances while writing with dd. I was
> using LUKS previously and I got only one dev mapper. Now I got 2. Does
> it have a big impact on performances?
>
> Kind regards.
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-10-12 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 11:56 LUKS2 - RAID0 - NVME : alignment issue laurent cop
2018-10-12 16:09 ` Ondrej Kozina [this message]
2018-10-18 17:51 ` Mikulas Patocka
2018-10-19 6:47 ` Milan Broz
2018-10-27 23:05 ` laurent cop
2018-11-04 16:33 ` Milan Broz
2018-10-18 18:43 ` Mike Snitzer
2018-10-19 6:43 ` Milan Broz
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=e93e5cdb-10be-8bec-b33b-150bad9a32ac@redhat.com \
--to=okozina@redhat.com \
--cc=dm-devel@redhat.com \
--cc=laurent.cop@gmail.com \
/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.