Gluster users - Feb 2010 - dkms-fuse and afr problems (was: Problems with gluster and autofs )

> I have a working glusterfs setup running on Centos 5.3 with
>
> glusterfs-2.0.4 (compiled from the source RPM)
> fuse-2.7.4-1
> dkms-fuse-2.7.4-1.rf
> autofs-5.0.1-0.rc2.102
> kernel ?2.6.18-128.1.10.el5
>
Sorry for the possible lame question, but what is that dkms-fuse good for?

I also find  some patches at
http://ftp.gluster.com/pub/gluster/glusterfs/fuse/ .

I can't find anything about these in the documentation. Maybe this is
the missing part from my setup.


I have the very same problem as Roland:

http://gluster.org/pipermail/gluster-users/2010-January/003731.html

I've set up 3.0.2 on freshly installed and updated CentOS 5.4  boxes
based on this doc: http://ewan.to/post/278951058/gluster-replication

I found that 'ls -lR' works to enforce the sync as long as the bottom
part of the client config is deleted (everything below the mirror).

I know about guys who made glusterfs 3.0 afr working as expected
(background self healing) on Debian. I'm wondering what
service/package/patch missing from CentOS to make it work.


Does anyone running GlusterFS 3.0.x on CentOS/Redhat with tested
background self-healing?
Is there any way to monitor the self-healing process?


Thanks,

miloska

On 10 Feb 2010, at 10:14, miloska at gmail.com wrote:
>> I have a working glusterfs setup running on Centos 5.3 with
>> 
>> glusterfs-2.0.4 (compiled from the source RPM)
>> fuse-2.7.4-1
>> dkms-fuse-2.7.4-1.rf
>> autofs-5.0.1-0.rc2.102
>> kernel  2.6.18-128.1.10.el5
>> 
> 
> Sorry for the possible lame question, but what is that dkms-fuse good for?
It allows auto-build of the fuse kernel module at boot time to match the running
kernel... saves having to manually re-compile the fuse kernel module every time
there's a kernel update..

Regards

Phil


-- 
Director, Layer3 Systems Ltd
Layer3 Systems Limited is registered in England.  Company no 3130393
43 Pendle Road, Streatham, London, SW16 6RT
tel: 020 8769 4484