Strange, I do have the fuse and gluster-fuse / gluster-core packages installed on the client. I can mount the volume using the gluster nas-srv-01:/users /users glusterfs defaults,_netdev 0 0 Maybe I just need to figure out how to configure builtin Gluster NFS to export like I want. I'm trying to ensure that from the Gluster servers, I have fine control over which ip addresses can mount specific parts of the volume, similar to what can be done via /etc/exports -----Original Message----- From: Burnash, James [mailto:jburnash at knight.com] Sent: Wednesday, March 30, 2011 12:34 PM To: Mike Hanby; Gluster-users at gluster.org Subject: RE: Disabling NFS Hi Mike. Using this method, you still need to have fuse on the NFS client, because what the regular NFS server exports is in fact the Gluster fuse filesystem. I know, because I went down this path as well. I believe that the purpose of the Gluster NFS server was to eliminate this dependency - which it does very well, in my experience. Hope this helps. James Burnash, Unix Engineering -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Mike Hanby Sent: Wednesday, March 30, 2011 1:21 PM To: Gluster-users at gluster.org Subject: [SPAM?] Disabling NFS Importance: Low Howdy, With 3.1.3 the option was added to disable the builtin Gluster NFS. Does that mean that the following scenario should work: 1. Disable Gluster NFS "gluster volume set <VOLUME> nfs.disable on" 2. Restart the gluster servers for good measure 3. On one of the gluster servers, mount the volume using the gluster fuse client: mkdir /export/users # In /etc/fstab add localhost:/users /export/users glusterfs defaults,_netdev 0 0 mount /export/users 4. Export the gluster mounted volume from the gluster server using CentOS 5.5 provided NFS server: cat /etc/exports /exports/users/someuser 192.168.2.10(rw,async,root_squash) 5. Start system provided NFS server on the gluster server, configure the firewall properly for NFS access 6. On the client machine, 192.168.2.10, check that the export is advertised: $ /usr/sbin/showmount -e nas-srv-01 Export list for nas-srv-01: /export/users/someuser 192.168.2.10 7. Mount it on the client 192.168.2.10 machine mount -t nfs nas-srv-01:/export/users/someuser /mnt/someuser mount: nas-srv-01:/export/users/someuser failed, reason given by server: Permission denied The server reports: Mar 30 11:59:50 nas-srv-01 mountd[20233]: authenticated mount request from 192.168.2.10:909 for /export/users/someuser (/export/users/someuser) Mar 30 11:59:50 nas-srv-01 mountd[20233]: Cannot export /export/users/someuser, possibly unsupported filesystem or fsid= required ================================= Mike Hanby mhanby at uab.edu UAB School of Engineering Information Systems Specialist II IT HPCS / Research Computing _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users DISCLAIMER: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com
