[pkg-cryptsetup-devel] Bug#554506: (ugly) patch which should fix dm-crypt-on-lvm setups

[Jonas Meurer]

Hey Alasdair,

thanks for your comments.

On 04/11/2010 Alasdair G Kergon wrote:
> If the complex processing doesn't work for everyone then yes, simplify
> it and activate everything always.
> 
> To do it the other way you need logic something like:
>    Every time you boot, check if the stack of devices necessary to be
> activated has changed, and if so, update the information for use next
> time it boots.
>    At boot time, try the last stack known to work first.  If it doesn't
> work, try any other different saved stacks from earlier boots.  If none
> of them work then fall back to activating everything.
> 
> In other words make the initramfs code robust enough to cope with
> the unexpected!

I now changed the initramfs code to always activate all volume groups:
both before cryptsetup in case the source device is not available, and
after cryptsetup in case the unlocked device contains lvm data.

this way, the complicated and error-prone volume group -guessing code is
not needed anymore.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20101108/b4daea11/attachment.pgp>