[dm-crypt] Cryptsetup bug
hd4pix at gmail.com
Fri Dec 30 03:46:19 CET 2016
/dev/sdb1: UUID="fc1abc36-a8f8-4ace-b324-77f9ddd037ea" TYPE="crypto_LUKS"
PARTLABEL="EFI System" PARTUUID="bacaef0b-61a8-4460-98e7-8a2251d78268"
/dev/sdb2: UUID="8f6b6ff5-2f49-4edf-a35b-0e8df82e1e44" TYPE="crypto_LUKS"
PARTLABEL="Linux filesystem" PARTUUID="a58cce87-f792-4e5b-8c35-b4210472f86c"
On Thu, Dec 29, 2016 at 9:18 PM, Milan Broz <gmazyland at gmail.com> wrote:
> On 12/29/2016 06:53 PM, Hunter DeMeyer wrote:
> > I believe that under certain circumstances cryptsetup will encrypt
> > more than one partion on a drive. I have attached the process that
> > produced this bug.
> Cryptsetup accesses only device that you specify.
> There are two options how could happen that LUKS device appeared on
> different partition:
> 1) there was some old LUKS device on the /dev/sdb1 offset start already or
> 2) you recreated partitions but for some reason kernel still see the old
> partitions size,
> and sdb1 was still in fact mapped to the old partition.
> Could you please paste blkid /dev/sdb* to verify it is the first option
> (to check LUKS UUID)?
> I guess you will see different UUIDs.
> And please do not send html mails to the list.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dm-crypt