Benjamin,

thanks for the report. Yes, there's a bug in the package scripts which leaves 
the old link behind - it should have been deleted. The links cannot be owned by 
a package.

As a workaround, running "/sbin/openafs-modules --clean-up" is a bit simpler 
than finding the dangling link yourself.

I'm working on a fix.

        Stephan

On 2014-04-10, at 19:53, Benjamin Moody <[email protected]> wrote:

> Installing yesterday's version of openafs (specifically the kernel
> module package, kmod-openafs-431) completely breaks AFS due to a
> broken symbolic link:
> 
> lrwxrwxrwx. 1 root root 63 Apr 10 12:51
> /lib/modules/2.6.32-431.11.2.el6.x86_64/updates/fs/openafs/openafs.ko
> -> /lib/modules/2.6.32-431.el6.x86_64/kernel/fs/openafs/openafs.ko
> 
> I don't know why this link exists to begin with (rpm claims the link
> is 'not owned by any package') but in any case it is pointing to the
> wrong path.
> 
> kmod-openafs-431-1.6.5.1-147.sl6.431.x86_64 installs the kernel module as
> /lib/modules/2.6.32-431.el6.x86_64/kernel/fs/openafs/openafs.ko
> 
> kmod-openafs-431-1.6.5.1-148.sl6.431.11.2.x86_64 installs it as
> /lib/modules/2.6.32-431.11.2.el6.x86_64/kernel/fs/openafs/openafs.ko
> 
> As a result, modprobe can't find the module.  Changing the symlink to
> point to the correct location appears to fix the problem.
> 
> Benjamin

-- 
Stephan Wiesand
DESY - DV -
Platanenallee 6
15738 Zeuthen, Germany

Reply via email to