Summary: | genkernel compiles non-working lvm binary | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Jinks <mjinks> |
Component: | [OLD] Core system | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michael Jinks
2011-07-30 03:39:01 UTC
(In reply to comment #0) > If I booted from a rescue disk, mounted my userland and chrooted into it > without /sys mounted, the genkernel-built lvm binary would throw an error, like > so: > > # ./lvm pvscan > /sys/block: opendir failed: No such file or directory > > ...followed by an accurate printout of my LVM volumes. But if I tried the same > thing with /sys mounted, I got no output at all. > > So, it sounds like genkernel is, for some reason, building an lvm static binary > to expect an incorrect layout under /sys, or something to that effect. Maybe > the old deprecated layout? > Strange, this works nice for me. There are some things to consider. CONFIG_SYSFS_DEPRECATED must be unset in your kernel config. If this is disabled in your kernel config, and it still will not work, can you maybe tell us the output from "cat /proc/mounts" when you are in the shell where lvm fails? Which versions of genkernel and LVM is this about? @mjinks The information we are currently missing here, I think, is: The version of genkernel (attaching /var/log/genkernel.log so we know what versions and how you invoked genkernel would be of big help) Your kernel config file (/usr/src/linux/.config) Content of /proc/mounts from the environment where lvm fails But I still think that you by mistake have enabled CONFIG_SYSFS_DEPRECATED* which breaks any system which has received updates since 2006, since /sys/block is one of the directories that seems to be moved around by that kernel config option. No response from user for >1 year. |