Bug#566965: lvm2 initscript breaks most "advanced" setups (e.g. stacked block devices) or booting via UUID/LABEL

Bastian Blank waldi at debian.org
Sun Sep 26 15:34:57 UTC 2010

severity 566965 normal

On Sun, Sep 26, 2010 at 03:50:25PM +0200, Christoph Anton Mitterer wrote:
> I've changed the title and increased the severity as this breaks so many
> setups.

Please explain.

> Bastian, could you please _strongly_ reconsider to correct the initramfs
> boot-script.

There is no correct one. Please be more specific.

> This is AFAIU a misconception of it. As $ROOT is the final device
> containting the root-filesystem.
> This must not necessarily be an LV, just imagine setups like:
> physical disk -> MD -> LV -> dm-crypt/LUKS -> ext4-root-fs

You need more information in this case. Please provide patches to supply
all the necessary information to the initramfs. However you are not
allowed to enable everything it gets the hand on.

> 2) As it expects some rather fixed device pathnames.
> This in addition breaks using things like UUID/LABEL, even if there are
> no stacked block devices.

The device name is already unique. More then UUID or LABEL, lvm support


Earth -- mother of the most beautiful women in the universe.
		-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

More information about the pkg-lvm-maintainers mailing list