Summary: | sys-fs/aufs2 - aufs.ko needs unknown symbol __lookup_one_len [...] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Konstantin Agouros <elwood> |
Component: | [OLD] Core system | Assignee: | Thomas Sachau <tommy> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Konstantin Agouros
2009-06-08 10:55:53 UTC
Please test with aufs2-0_p20090601-r1 (in tree after your next regular sync) and report back. Hmmm how do I emerge an ebuild that is masked because of missing keyword? Konstantin Sorry, missed the keyword for x86, just added it, so should be there for your next scheduled sync. Hi, still does not work: * Updating module dependencies for 2.6.29-gentoo-r5 ... WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol __lookup_one_len WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol do_splice_to WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol devcgroup_inode_permission WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol lookup_hash WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol fsync_super WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol do_splice_from WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol do_truncate WARNING: //lib/modules/2.6.29-gentoo-r5/misc/aufs.ko needs unknown symbol deny_write_access [ ok ] * Adding module to moduledb. and after modprobe aufs2 dmesg says: aufs: Unknown symbol __lookup_one_len aufs: Unknown symbol do_splice_to aufs: Unknown symbol devcgroup_inode_permission aufs: Unknown symbol lookup_hash aufs: Unknown symbol fsync_super aufs: Unknown symbol do_splice_from aufs: Unknown symbol do_truncate aufs: Unknown symbol deny_write_access Do I need to add something to my kernel-config? Did you compile your patched kernel and booted it before loading the aufs2 module? What do You mean 'patched kernel' did the aufs ebuild patch something in /usr/src/linux that requires a reboot? If yes I did not, and this might explain it :) regards, Konstantin (In reply to comment #6) > What do You mean 'patched kernel' did the aufs ebuild patch something in > /usr/src/linux that requires a reboot? If yes I did not, and this might explain > it :) > > regards, > > Konstantin > The first ebuilds did patch the kernel dir with a note during compile. So if you did use an ebuild prior to 0_p20090601-r1, then it will be patched. With the current version, it will ask you to either patch it manually or enable the "kernel-patch" useflag, if the kernel is not already patched. So yes, you have to run all steps needed to compile, install and boot the current kernel again, then it should work. Please report back after that. OK this works. Just that I have the problem that it seems aufs doesn't work with xfs which is used on the box I am testing with, but this is another problem. Thanks Konstantin (In reply to comment #8) > OK this works. Just that I have the problem that it seems aufs doesn't work > with xfs which is used on the box I am testing with, but this is another > problem. > > Thanks Konstantin > For this, i would suggest you to create a simple way to reproduce your problem, than ask on the aufs mailing list. The author is responsive and very helpfull whereever it is possible for him. ;-) Closing this bug as invalid since the reason was not in the source nor in the ebuild. |