for some odd reason, module_dir is no longer being defined by redhat-cluster (GFS) sources. Now, what happens after emerge gfs-kernel-1.03, is that the compiled modules are installed to '/' instead of '/lib/modules/${KV_FULL} for example, '/fs/gfs/gfs.ko' is merged to '/', creating a "/fs" directory on '/', where it should actually be installing to /lib/modules/${KV_FULL}/fs/gfs/gfs.ko I found the problem started happening last month (after portage update) with all the following packages: sys-cluster/cman-kernel-1.03 sys-cluster/dlm-kernel-1.03 sys-cluster/gfs-kernel-1.03 sys-cluster/gnbd-kernel-1.03 Solution: In the source_install() of the ebuild file, change this: emake DESTDIR=${D} install || die "install error" to this: emake DESTDIR=${D} module_dir=${D}/lib/modules/${KV_FULL} install || die "install error" I will make a seperate bug report for sys-cluster/gnbd-kernel-1.03 because it also failed to compile because of devfs stuff which breaks the compile against recent kernels with udev (ebuild requires 2.6.16 or higher kernel anyways, tested with 2.6.17-gentoo-r8), so requires additional patch to the source
Created attachment 104379 [details, diff] sys-cluster/cman-kernel ebuild patch
*** Bug 156526 has been marked as a duplicate of this bug. ***
Created attachment 104380 [details, diff] sys-cluster/dlm-kernel ebuild patch
Created attachment 104381 [details, diff] sys-cluster/gfs-kernel ebuild patch
cman-kernel and dlm-kernel are fixed in CVS. I don't use gfs or gndb, but I'll fix those soon if no one else does.
gfs and gndb fixed.