> There is no way to resolve such conflicts automatically. In some cases (such as the case above), there is.
> We would risk serious data loss. The very worst that could eventually happen here is that the swap is mounted unencrypted. The only possible data loss is that LUKS key slots would be overwritten. That is, if the partition is exposed as "swap". But that's not what I suggest. I suggest that when there is a valid LUKS header, the partition is always exposed as LUKS. There is no possible data loss here: if there is no valid key, the partition cannot be used at all. > Be happy, that the system did not recognize one of your data partitions as swap and corrupted it. It's not a data partition that has a swap signature, it's an actual swap partition (but encrypted with LUKS), with type 0x83 "swap". And it worked that way for about two years (the UUID that was exposed in /dev/disks/by-uuid was the one of the swap header, not the LUKS header). And nothing bad happened, until Jaunty, where I could not boot at all. Proven fact: your position, on this particular issue, breaks things. Still not proven: my suggestion would break things. To do: - prove that my suggestion to expose the LUKS UUID could actually cause bad things OR - recognize that this is an acceptable way to deal with that particular issue (way better IMO than to actually write things on block devices without knowing too well if you should do that, think of the users). -- udev fails to identify crypt_LUKS swap partition by uuid https://bugs.launchpad.net/bugs/362315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
