Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 255196
Alias:
Product:
Component:
Status: NEW
Resolution:
Assigned To: Gentoo Genkernel Maintainers <genkernel@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Robert Buchholz <rbu@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 255196 depends on: 207612 Show dependency tree
Bug 255196 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.








View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2009-01-16 20:03 0000 
If the internal copy of LVM2 is used (which is 2.02.28), one can get the same
errors as reported in bug 207612. Please bump and use a later copy of LVM2
(2.02.37 is stable currently).

------- Comment #1 From Ahmed Ammar 2009-02-27 13:12:13 0000 ------- 
I second this.

------- Comment #2 From Andrew Gaffney 2009-02-27 13:36:21 0000 ------- 
You can second this all you want. Have you actually bumped the version in
genkernel.conf and tried build an initramfs with it and booting?

------- Comment #3 From Robert Buchholz 2009-03-01 11:26:57 0000 ------- 
I have seen the failures using the internally specified copy. Then I installed
the latest ebuild and it used the system copy, which booted. I have not tried
editing it so it uses the latest version as an internal copy -- does that cause
problems?

------- Comment #4 From Denis Dupeyron 2009-07-22 00:14:38 0000 ------- 
I emerged genkernel-9999 today (to get the fix for bug #276753), bumped LVM to
latest stable i.e. 2.02.36 in genkernel.conf and it properly booted my
RAID+LUKS+LVM system with hardened-sources-2.6.29. I had previously experienced
this issue on 2 other systems although I didn't try on this one without bumping
LVM.

Denis.

------- Comment #5 From Andrew Gaffney 2009-07-22 13:06:58 0000 ------- 
And you're sure that you moved your system lvm and lvm.static binaries out of
the way so that it would compile lvm internally?

------- Comment #6 From Christian Bricart 2009-07-23 13:10:35 0000 ------- 
actually people (still) having CONFIG_SYSFS_DEPRECATED or the newer
CONFIG_SYSFS_DEPRECATED_V2 set in their kernel will not suffer from this bug.

bumping genkernel's internal versions to:

DEVICE_MAPPER_VER="1.02.24"
LVM_VER="2.02.31"

in /etc/genkernel.conf resolves the issue which has not been related to lvm vs.
lvm.static at any time but the way block devices are listed in sysfs (i.e.
/sys/block/* have become symlinks and older versions of LVM simply ignore
rather than follow them).

as a side note: I've tried even higher version numbers of LVM here - but they
all failed to compile from within calling "genkernel ramdisk"..

------- Comment #7 From Christian Bricart 2009-07-23 13:57:45 0000 ------- 
to sum things up that means to:

- bump the internal version numbers in genkernel.conf to address people that do
not have USE=static on sys-fs/lvm2 and/or use >=lvm2-2.02.48-r1 with
<genkernel-9999 (wrt bug #276753)

- stablize >=genkernel-3.4.10.905-r1 (which then has bug #276753 fixed)

------- Comment #8 From François Valenduc 2009-11-11 12:21:23 0000 ------- 
lvm2-2.02.51-r1 became stable for x86. It tooks me hours to find that I had to
update genkernel to be able to boot my system again because I have my root
partition in a LVM2 volume. So, I think it's quite urgent to stablize
>=genkernel-3.4.10.905-r1.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug