On Mon, 04 Nov 2024 at 17:43:07 +0000, Tj wrote: > This really is not an lvm problem; lvm never should try to activate an > incomplete volume group especially if some of the logical volumes span > the physical volume that is missing - and that is the case here due to > the cryptroot hook script not ensuring all PVs within an encrypted > container are configured to unlock.
On a sid system, after creating a new PV and extending the LV holding / to use some of its extents, the new PV shows up in its slaves devices and is configured to unlock at initramfs stage. > I wrote a small patch yesterday that handles it correctly. I need to > work up some tests to ensure it doesn't cause any regressions elsewhere > but it is quite simple. > > I'll add a merge request once it is ready. I'm reluctant to accept LVM-specific handling for what I consider a regression outside src:cryptsetup. -- Guilhem.
signature.asc
Description: PGP signature
