Hi Anthony, sub directory mount is not possible with GlusterNfs in 3.2.x version. you can get the 3.3 gNfs to work for subdir mount on solaris, though it requires some oblique steps to get it working. The steps are provided in the documentation (Admin guide i think) for 3.3.
Regards, Rajesh Amaravathi, Software Engineer, GlusterFS RedHat Inc. ----- Original Message ----- From: "anthony garnier" <sokar6...@hotmail.com> To: sgo...@redhat.com Cc: gluster-users@gluster.org Sent: Thursday, July 19, 2012 12:50:41 PM Subject: Re: [Gluster-users] NFS subdirectory Solaris client Hi Shishir, I have reconfigured the port to 2049 so there is no need to specify it. Moreover the mount of the volume works fine, it's only the mount of the subdirectory that doesn't work. Thx and Regards, Anthony > Date: Wed, 18 Jul 2012 22:54:28 -0400 > From: sgo...@redhat.com > To: sokar6...@hotmail.com > CC: gluster-users@gluster.org > Subject: Re: [Gluster-users] NFS subdirectory Solaris client > > Hi Anthony, > > Please also specify this option port=38467, and try mounting it. > > With regards, > Shishir > > ----- Original Message ----- > From: "anthony garnier" <sokar6...@hotmail.com> > To: gluster-users@gluster.org > Sent: Wednesday, July 18, 2012 3:21:36 PM > Subject: [Gluster-users] NFS subdirectory Solaris client > > > > Hi everyone, > > I still have problem to mount subdirectory in NFS on Solaris client : > > # mount -o proto=tcp,vers=3 nfs://yval1010:/test/test2 /users/glusterfs_mnt > nfs mount: yval1010: : RPC: Program not registered > nfs mount: retrying: /users/glusterfs_mnt > > > [2012-07-18 11:43:43.484994] E [nfs3.c:305:__nfs3_get_volume_id] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup+0x125) > [0x7f5418ea4e15] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup_reply+0x48) > [0x7f5418e9b908] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_request_xlator_deviceid+0x4c) > [0x7f5418e9a54c]))) 0-nfs-nfsv3: invalid argument: xl > [2012-07-18 11:43:43.491088] E [nfs3.c:305:__nfs3_get_volume_id] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup+0x125) > [0x7f5418ea4e15] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup_reply+0x48) > [0x7f5418e9b908] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_request_xlator_deviceid+0x4c) > [0x7f5418e9a54c]))) 0-nfs-nfsv3: invalid argument: xl > [2012-07-18 11:43:48.494268] E [nfs3.c:305:__nfs3_get_volume_id] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup+0x125) > [0x7f5418ea4e15] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup_reply+0x48) > [0x7f5418e9b908] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_request_xlator_deviceid+0x4c) > [0x7f5418e9a54c]))) 0-nfs-nfsv3: invalid argument: xl > [2012-07-18 11:43:48.992370] W [socket.c:195:__socket_rwv] > 0-socket.nfs-server: readv failed (Connection reset by peer) > [2012-07-18 11:43:57.422070] W [socket.c:195:__socket_rwv] > 0-socket.nfs-server: readv failed (Connection reset by peer) > [2012-07-18 11:43:58.498666] E [nfs3.c:305:__nfs3_get_volume_id] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup+0x125) > [0x7f5418ea4e15] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_lookup_reply+0x48) > [0x7f5418e9b908] > (-->/usr/local/lib//glusterfs/3.3.0/xlator/nfs/server.so(nfs3_request_xlator_deviceid+0x4c) > [0x7f5418e9a54c]))) 0-nfs-nfsv3: invalid argument: xl > > > Can someone confirm that ? > > Regards, > > Anthony > > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
