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: sgowda at redhat.com > To: sokar6012 at hotmail.com > CC: gluster-users at gluster.org > Subject: Re: 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" <sokar6012 at hotmail.com> > To: gluster-users at gluster.org > Sent: Wednesday, July 18, 2012 3:21:36 PM > Subject: 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 at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20120719/3a9f5f54/attachment.htm>
