[Gluster-users] Solaris NFS client and nfs.rpc

[Justin Clift]

Side note... please don't email stuff to "gluster-users-bounces at gluster.org"
(with the "-bounces" on the end of the address). :)

Stuff to -bounces goes to the mailing list admins (so no real use), and I
suspect it also mucks up member processing. (not totally sure tho)

Regards and best wishes,

Justin Clift


On 11/10/2013, at 5:11 PM, Olivier.Franki at smals.be wrote:
> Hello Heiko, 
> 
> 
> >you should start the call with better overview.
> > (client-ip client-os  Server-ip server-os action result...) 
> 
> What we try to do is 
> 
> Client      OS         Server      Command                                            Expected           Result 
> 99.200      RHEL6      gfs-3.4.1   mount -t nfs -o vers=3 10.1.99.202:/vol1 /mnt      Access Denied      OK 
> 99.201      Solaris10  gfs-3.4.1   mount -o vers=3 nfs://10.1.99.202:/vol1 /mnt       Mount done         OK 
> 98.66       Solaris10  gfs-3.4.1   mount -o vers=3 nfs://10.1.99.202:/vol1 /mnt       Access Denied      NOK, mount is done
> 
> Normally, only 99.201 should be able to mount via NFS (we mount linux clients via glusterfs) 
> 
> 
> [root at llsmagfs001a glusterfs]# gluster volume info vol1 
> 
> Volume Name: vol1 
> Type: Distribute 
> Volume ID: 4abcee08-6172-441a-851b-53becb77c281 
> Status: Started 
> Number of Bricks: 1 
> Transport-type: tcp 
> Bricks: 
> Brick1: llsmagfs001a.cloud.testsc.sc:/export/vol1 
> Options Reconfigured: 
> diagnostics.client-log-level: DEBUG 
> diagnostics.brick-log-level: DEBUG 
> auth.allow: 10.1.99.200 
> nfs.rpc-auth-allow: 10.1.99.201 
> diagnostics.client-sys-log-level: WARNING 
> diagnostics.brick-sys-log-level: WARNING 
> 
> 
> > Do check running "one" nfsd on nfsserver only. [1]
> > 
> > nfs.rpc-auth-allow: 10.1.99.201
> > all clients should be added.
> > 
> > i had to use the following command on solaris-client:
> > 
> > nfsserver #  gluster volume status | grep NFS
> > NFS Server on localhost                                 38467   Y       20092
> > NFS Server on 192.168.5.153                             38467   Y       9281
> > ## pick port number
> > nfsclient # mount nfs://$nfsserver:38467/$vol /mnt/$vol 
> 
> 
> We use gluster 4.1, so the NFS server is started on port default port 2049 and there is no other NFS server started on gluster nodes 
> 
> [root at llsmagfs001a ~]# netstat -plantu |grep 2049 
> tcp        0      0 0.0.0.0:2049                0.0.0.0:*                   LISTEN      15432/glusterfs 
> 
> 
> [root at llsmagfs001a ~]# gluster volume status |grep NFS 
> NFS Server on localhost                                 2049    Y       15432 
> NFS Server on llsmagfs001d.cloud.testsc.sc              2049    Y       15257 
> NFS Server on llsmagfs001b.cloud.testsc.sc              2049    Y       15287 
> NFS Server on llsmagfs001c.cloud.testsc.sc              2049    Y       15379 
> 
> Regards, 
> 
> Olivier 
> 
> 
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users

--
Open Source and Standards @ Red Hat

twitter.com/realjustinclift