[CentOS] Wherefore is FUSE?

[Johnny Hughes]

Benjamin Smith wrote:
> Tonight, I tried to roll out fuse on my CentOS 4 production system. (in order 
> to use GlusterFS) 
> 
> I have two identical servers, and one took, the other didn't. 
> 
> How simple could this be? 
> 
> # yum install yum-plugin-priorities 
> # yum install rpmforge-release
> # yum install fuse dkms-fuse 
> 
> both of these seem to work. Yet I run 
> 
> [root at kepler drivers]# modprobe fuse
> FATAL: Module fuse not found.
> 
> I don't get it. both sides have the same: 
> WORKS: 
> [root at koehl etc]# rpm -qa | grep -i rpmforge
> rpmforge-release-0.3.6-1.el4.rf
> [root at koehl etc]# rpm -qa | grep -i fuse
> fuse-2.7.3-1.el4.rf
> dkms-fuse-2.7.2-1.nodist.rf
> [root at koehl etc]# modprobe fuse
> [root at koehl etc]# rpm -qa | grep -i pri
> yum-plugin-priorities-0.0.7-1.el4.centos
> [root at koehl etc]# 
> ls /lib/modules/2.6.9-67.0.7.ELsmp/kernel/drivers/fs/fuse/fuse.ko
> /lib/modules/2.6.9-67.0.7.ELsmp/kernel/drivers/fs/fuse/fuse.ko
> [root at koehl etc]# 
> lib/modules/2.6.9-67.0.7.ELsmp/kernel/drivers/fs/fuse/fuse.ko
> [root at koehl drivers]# 
> rpm -qf /lib/modules/2.6.9-67.0.7.ELsmp/kernel/drivers/fs/fuse/fuse.ko
> file /lib/modules/2.6.9-67.0.7.ELsmp/kernel/drivers/fs/fuse/fuse.ko is not 
> owned by any package
> 
> 
> NOT WORKS: 
> [root at kepler drivers]# rpm -qa | grep -i rpmforge
> rpmforge-release-0.3.6-1.el4.rf
> [root at kepler drivers]# rpm -qa | grep -i fuse
> dkms-fuse-2.7.2-1.nodist.rf
> fuse-2.7.3-1.el4.rf
> [root at kepler drivers]# modprobe fuse
> FATAL: Module fuse not found.
> [root at kepler /]# 
> ls /lib/modules/2.6.9-67.0.7.ELsmp/kernel/drivers/fs/fuse/fuse.ko
> ls: /lib/modules/2.6.9-67.0.7.ELsmp/kernel/drivers/fs/fuse/fuse.ko: No such 
> file or directory
> 
> Why one and not the other? And why isn't the fuse kernel "owned" by the rpm I 
> used to install it? It's driving me NUTS. I've already tried copying over 
> the "fs" directory and all child leaves. No effect.  

This one is an easy answer ... the whole purpose of a DKMS is to BUILD 
modules when you CHANGE your kernel.  These modules are not INSTALLED, 
they are BUILT (generated) so they will never be owned by any RPM.

In order for this to work, you have to have the kernel-smp-devel for the 
  kernel that you want to boot installed so that fuse can generate the 
module.  The exact version is important ... on the one where it did not 
build, make sure that your have the proper kernel-smp-devel installed 
with the commands:

uname -r
(the result will be a version)

rpm -q kernel-smp-devel
(make sure the versions match)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos/attachments/20080412/e5e2c066/attachment.sig>