Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 323253

Summary: sys-boot/lilo-22.8-r2: installation of the bootloader on top of LVM2 may fail
Product: Gentoo Linux Reporter: Constantin Baranov <const>
Component: [OLD] Core systemAssignee: Gentoo's Team for Core System packages <base-system>
Status: RESOLVED FIXED    
Severity: major CC: xmw
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on: 328441    
Bug Blocks:    
Attachments: Use just path to device.

Description Constantin Baranov 2010-06-08 20:30:11 UTC
DM library expects a device be called either by target name
or by full device node path name. But LILO uses just name
of device node after recursive symlink resolution.
That accidentally works on old lvm2/udev layout
(/dev/mapper/target nodes), but fails on the latest
layout (/dev/dm-N nodes).

Reproducible: Always

Steps to Reproduce:
Comment 1 Constantin Baranov 2010-06-08 20:33:48 UTC
Created attachment 234587 [details, diff]
Use just path to device.

This patch removes wrong algorithm and lets LILO
to name devices by full path either directly to device node
or to symlink. Both cases are OK to latest DM.
I didn't check if this is compatible with older DM.
Comment 2 Michael Weber (RETIRED) gentoo-dev 2010-06-09 00:58:37 UTC
Hi Constantine,

where is this patch from? Does upstream know about it?

Michael
Comment 3 Constantin Baranov 2010-06-09 07:30:05 UTC
(In reply to comment #2)
> where is this patch from? Does upstream know about it?

I've created this patch yesterday. I don't know where the upstream is,
lilo's homepage is dead. I posted the patch only here.
Comment 4 Tony Vroon (RETIRED) gentoo-dev 2010-06-09 13:33:22 UTC
Don't do that. Single issue, single bug. There is an existing bug for that other issue.
Comment 5 Constantin Baranov 2010-07-15 16:44:49 UTC
It seems that bug is fixed in lilo-23.0.
Comment 6 Samuli Suominen (RETIRED) gentoo-dev 2013-07-28 10:07:25 UTC
(In reply to Constantin Baranov from comment #5)
> It seems that bug is fixed in lilo-23.0.

Closing then because 23.2 is marked stable.