I see that this bug was created with Ubuntu 18.10 (judging by the tags).
I am trying to reproduce the issue on Ubuntu 19.04 (current development release).
I am failing to produce a mixed blocksize cryptsetup device:
$ sudo cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1
is failing for me with:
"Device size is not aligned to the requested sector size."
And on this machine, I do not have access to native 4k and non-4k drives at the same time. Let me get a better machine to debug this further.
I see that this bug was created with Ubuntu 18.10 (judging by the tags).
I am trying to reproduce the issue on Ubuntu 19.04 (current development release).
I am failing to produce a mixed blocksize cryptsetup device:
$ sudo cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1
is failing for me with:
"Device size is not aligned to the requested sector size."
And on this machine, I do not have access to native 4k and non-4k drives at the same time. Let me get a better machine to debug this further.