Comment 4 for bug 1810235
Revision history for this message
| Andreas Hasenack (ahasenack) wrote Re: cryptsetup silently fails in live environment | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
Could this be solved with different ordering? Luks first, then bcache? Luks definitely expects its header to be in a certain position:
LUKS EXTENSION
LUKS, the Linux Unified Key Setup, is a standard for disk encryption. It adds a standardized header at the start of the device, a key-slot area directly behind the header and the bulk data area behind that. The
whole set is called a 'LUKS container'. The device that a LUKS container resides on is called a 'LUKS device'. For most purposes, both terms can be used interchangeably. But note that when the LUKS header is at
a nonzero offset in a device, then the device is not a LUKS device anymore, but has a LUKS container stored in it at an offset.