84068 – device-mapper-1.01 breaks lvm2 on reboot

Bug 84068 - device-mapper-1.01 breaks lvm2 on reboot

Summary: device-mapper-1.01 breaks lvm2 on reboot

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	x86 Linux

Importance:	High critical
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-03-04 03:52 UTC by Harris Landgarten
Modified:	2005-03-04 04:45 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Harris Landgarten 2005-03-04 03:52:25 UTC

lvm2 links to libdevmapper.so.1.00 which is replaced by /lib/libdevmapper.so.1.01 by the new ebuild. This causes lvm2 to fail on the next reboot unless lvm2 is re-emerged.

Work around to boot after boot fails: 
ln -sf /lib/libdevmapper.so.1.01 /lib/libdevmapper.so.1.00

After booting lvm2 should be re-emerged to fix dependencies.

revdep-rebuild does not pick this problem up and the ebuild makes no mention of it.

Reproducible: Always
Steps to Reproduce:
1.see desc
2.
3.

Actual Results:  
all lvm2 tool broken and lv volumes will not mount on reboot

Comment 1 Carsten Lohrke (RETIRED) gentoo-dev

2005-03-04 04:45:49 UTC

Portage isn't able to care for reverse dependencies (yet). At least if you emerge system critical libs, you should always run `revdep-rebuild` afterwards.