This happens when a lookup on Path (in this case "/home/alok/cache_dir") failed in the FSAL. Since the FSAL is proxy, it tried to do a remote lookup of that path on the remote server, and this failed. Is this path exported via NFSv4 on 10.1.10.103? Daniel On 1/6/20 10:40 AM, Alok Sinha wrote: > > > NFS ganesha version : 2.8.3 > > I can mount the directory: > > alok@spillbox:src$ df -k /home/alok/cache_dir > Filesystem 1K-blocks Used Available Use% > Mounted on > 10.1.10.103:/home/alok/cache_dir/ 427548672 16504832 389255168 5% > /home/alok/cache_dir > alok@spillbox:src$ > > > ganesha.conf entry: > > EXPORT > { > Export_Id = 12345; > Path = "/home/alok/cache_dir"; > Pseudo = "/home/alok/cache_dir"; > Access_Type = RW; > Squash = no_root_squash; > FSAL { > Name = PROXY; > Srv_Addr = 10.1.10.103; > Use_Privileged_Client_Port = true; > } > } > > > I get : > 06/01/2020 07:34:30 : epoch 5e135386 : spillbox : > ganesha.nfsd-9031[main] init_export_root :EXPORT : > CRIT :Lookup failed on path, ExportId=12345 Path=/home/alok/cache_dir > FSAL_ERROR=(No such file or di > rectory,2) > > I am stuck. Any clue? > > -alok > > _______________________________________________ > Devel mailing list -- devel(a)lists.nfs-ganesha.org > To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org

Mount (the MNT protocol) is only for NFSv3. NFSv4 doesn't use that protocol, it uses a pseudoroot and NFS ops. So you won't see any mount traffic from Ganesha when it's doing proxy, only NFSv4 traffic. Daniel On 1/6/20 2:01 PM, Alok Sinha wrote: > > > Hi Daniel, > > Thanks for the pointer. > > NFS version does not look like an issue. Real issue may be following: > > I started mountd in debug mode on NFS server. "mount" from command > shows that > calls are reaching to mountd on NFS server. But from NFS Ganasha, it > looks to me that calls are not > reaching to mountd on NFS server. There is no logging/activity on NFS > server. > > Any clue? > > I have used NFS proxy successfully before with older version of Ganesha. > > -alok > > > On Mon, Jan 6, 2020 at 7:55 AM Daniel Gryniewicz <dgryniew(a)redhat.com > <mailto:dgryniew@redhat.com>> wrote: > > This happens when a lookup on Path (in this case > "/home/alok/cache_dir") > failed in the FSAL. Since the FSAL is proxy, it tried to do a remote > lookup of that path on the remote server, and this failed. Is > this path > exported via NFSv4 on 10.1.10.103? > > > Daniel > > On 1/6/20 10:40 AM, Alok Sinha wrote: > > > > > > NFS ganesha version : 2.8.3 > > > > I can mount the directory: > > > > alok@spillbox:src$ df -k /home/alok/cache_dir > > Filesystem 1K-blocks Used Available Use% > > Mounted on > > 10.1.10.103:/home/alok/cache_dir/ 427548672 16504832 389255168 5% > > /home/alok/cache_dir > > alok@spillbox:src$ > > > > > > ganesha.conf entry: > > > > EXPORT > > { > > Export_Id = 12345; > > Path = "/home/alok/cache_dir"; > > Pseudo = "/home/alok/cache_dir"; > > Access_Type = RW; > > Squash = no_root_squash; > > FSAL { > > Name = PROXY; > > Srv_Addr = 10.1.10.103; > > Use_Privileged_Client_Port = true; > > } > > } > > > > > > I get : > > 06/01/2020 07:34:30 : epoch 5e135386 : spillbox : > > ganesha.nfsd-9031[main] init_export_root :EXPORT : > > CRIT :Lookup failed on path, ExportId=12345 > Path=/home/alok/cache_dir > > FSAL_ERROR=(No such file or di > > rectory,2) > > > > I am stuck. Any clue? > > > > -alok > > > > _______________________________________________ > > Devel mailing list -- devel(a)lists.nfs-ganesha.org > <mailto:devel@lists.nfs-ganesha.org> > > To unsubscribe send an email to > devel-leave(a)lists.nfs-ganesha.org > <mailto:devel-leave@lists.nfs-ganesha.org> > > > > -- > Alok Sinha > Founder, Spillbox