The error message that you're getting is consistent with the kernel module failing to register the AFS system calls. The AFS client programs are then trying to make system calls that don't exist, which result in various odd errors such as the ones you're seeing.
I'm a little confused by the output you're seeing, given that loading the AFS kernel module should result in a message saying that it taints the kernel and starting afsd should produce information about the cache, neither of which are happening. Are you just not showing all of the output that you're getting, or are you missing some output? If you have an old kernel module installed that was never fully removed from the kernel, things like this can happen. Sometimes AFS doesn't want to unload cleanly and the machine has to be rebooted to get back to a consistent state, although that's fairly rare these days. dmesg output may also be useful, in particular the lines about searching for the system call table. Again, I don't understand why you're not seeing that output when you start the AFS client for the first time after boot. -- openafs gives segfault on kernel 2.6.22-13 https://bugs.launchpad.net/bugs/150469 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
