[Gluster-users] NFS subdirectory Solaris client

[Rajesh Amaravathi]

fwding from krishna's mail, need to update the docs with this info:

Here are the steps:
on linux client machine:
* make sure you have the directory you want to export is already created, if 
not create it.
  if /mnt/nfs is the mount point do this:
  mkdir /mnt/nfs/subdir
* on storage node do:
  gluster volume set <volname> nfs.export-dir /subdir
  gluster volume set <volname> nfs.mount-udp on
* do a "showmount -e <storage-node-ip>" to see that subdir is exported too.
* on a LINUX client do this:
  mount -o proto=tcp <storage-node-ip>:/<volname>/subdir /mnt/nfs
  i.e you are mounting the subdir.
* now on SOLARIS client do this:
  mount nfs://<storage-node-ip>:/<volname>/subdir /mnt/nfs
  you should be able to access the exported subdir on Solaris machine. note 
that you have to mount the subdir on a linux machine first with proto=tcp 
before trying to mount on solaris machine.

Regards, 
Rajesh Amaravathi, 
Software Engineer, GlusterFS 
RedHat Inc. 

----- Original Message -----
From: "anthony garnier" <sokar6012 at hotmail.com>
To: rajesh at redhat.com
Cc: gluster-users at gluster.org, sgowda at redhat.com
Sent: Thursday, July 19, 2012 2:19:24 PM
Subject: RE: [Gluster-users] NFS subdirectory Solaris client


Hi Rajesh , 
My mistake, I didn't specify that I was in 3.3. 
I didn't see any particular comment in the Admin doc about subdirectory export. 
Are you referring to this option: nfs.export-dir, but by default every subdirectory are exported. 

Regards, 

Anthony 




> Date: Thu, 19 Jul 2012 04:42:20 -0400 
> From: rajesh at redhat.com 
> To: sokar6012 at hotmail.com 
> CC: gluster-users at gluster.org; sgowda at redhat.com 
> Subject: Re: [Gluster-users] NFS subdirectory Solaris client 
> 
> 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" <sokar6012 at hotmail.com> 
> To: sgowda at redhat.com 
> Cc: gluster-users at 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: sgowda at redhat.com 
> > To: sokar6012 at hotmail.com 
> > CC: gluster-users at 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" <sokar6012 at hotmail.com> 
> > To: gluster-users at 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 at gluster.org 
> > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users 
> 
> _______________________________________________ 
> Gluster-users mailing list 
> Gluster-users at gluster.org 
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users