[Gluster-users] Issue with geo-replication and nfs auth

[Cedric Lagneau]

hi,

I've some issue with geo-replication (since 3.2.0) and nfs auth (since initial release).


Geo-replication 
---------------
System : Debian 6.0 amd64
Glusterfs: 3.2.0

MASTER (volume) => SLAVE (directory)
For some volume it works, but for others i can't enable geo-replication and have this error with a faulty status:
2011-05-03 09:57:40.315774] E [syncdutils:131:log_raise_exception] <top>: FAIL:
Traceback (most recent call last):
  File "/usr/lib/glusterfs/glusterfs/python/syncdaemon/syncdutils.py", line 152, in twrap
    tf(*aa)
  File "/usr/lib/glusterfs/glusterfs/python/syncdaemon/repce.py", line 118, in listen
    rid, exc, res = recv(self.inf)
  File "/usr/lib/glusterfs/glusterfs/python/syncdaemon/repce.py", line 42, in recv
    return pickle.load(inf)
EOFError

Command line : 
gluster volume geo-replication test slave.mydomain.com:/data/test/ start

On /etc/glusterd i don't see any diff between /etc/glusterd files.

#gluster volume geo-replication status
MASTER               SLAVE                                              STATUS    
--------------------------------------------------------------------------------
test                 ssh://root@slave.mydomain.com:file:///data/test        faulty        
test2                ssh://root@slave.mydomain.com:file:///data/test2       OK        



NFS auth allow 
--------------
Even if i set nfs.rpc-auth-allow on volume to restrict acces on some ip i can always mount via nfs. How it works ?

Sample:

#gluster volume set test nfs.rpc-auth-allow 10.0.0.10
#gluster volume info test
Options Reconfigured:
nfs.rpc-auth-allow: 10.0.0.10

My client ip 192.168.10.25 can mount the test volume with nfs with:
mount -t nfs -o vers=3 glusterserveur:/test /mnt/test


thanks for your help,


best regards,


-- 

Cédric Lagneau