Re: Unlocking LUKS2 with Sector Size > 512B

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Thanks Michael,

I couldn't figure out how to find that Message-ID, but I did a bit more digging.

I found that dm-crypt.c in the kernel has an internal version number that cryptsetup can query.
The required support for sector_size turns up in kernel v4.12

mh

On Mon, Nov 26, 2018 at 1:31 PM Michael Kjörling <michael@xxxxxxxxxxx> wrote:
On 26 Nov 2018 12:51 -0500, from mort@xxxxxxxx (Martin Hicks):
> [ 2807.225522] device-mapper: table: 254:0: crypt: Invalid feature arguments
> device-mapper: reload ioctl on  failed: Invalid argument
> Requested sector_size option is not supported.

Might this be related to what Milan Broz discussed the other day
in Message-ID: <aa607562-adad-6aaa-1865-df1e43eea44a@xxxxxxxxx>?

--
Michael Kjörling • https://michael.kjorling.semichael@xxxxxxxxxxx
  “The most dangerous thought that you can have as a creative person
              is to think you know what you’re doing.” (Bret Victor)
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
https://www.saout.de/mailman/listinfo/dm-crypt


--
Martin Hicks P.Eng.      |         mort@xxxxxxxx
Bork Consulting Inc.     |   +1 (613) 266-2296
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
https://www.saout.de/mailman/listinfo/dm-crypt

[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux