> I''ve been trying to bring up the nfs-ganesha PROXY FSAL without success.
> I'm having difficulty with both the 2.5 community release and when
building
> from source. I tried previous releases but was getting config file
errors. With
> 2.5 I'm getting an NFS4 permission error when starting nfs-ganesha where
it
> appears to be validating the pseudo export path. I saw a message on the
> mailing list just yesterday that the PROXY code seems stable, so I'm
> suspecting it's something that I'm doing. Does the proxy functionality
work?
> If it does, can someone look at the configuration below and let me know if
> I'm doing something wrong? If apologize if this the wrong place to post
this.
>
> On Centos 6.7 NFS server (192.168.1.30):
>
> # exportfs -v
> export/test
> 192.168.1.0/24(rw,async,wdelay,no_root_squash,no_subtree_check,sec=sys
> ,rw,no_root_squash,no_all_squash)
>
> Centos 7.2 client NFS connection test:
>
> $ sudo mount -v -t nfs4 192.168.1.30:/export/test /mnt/test
> $ mount | grep 1.30
> 192.168.1.30:/export/test on /mnt/test type nfs4
> (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto
> =tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.9,local_lock=
> none,addr=192.168.1.30)
>
> Contents of ganesha.conf on Centos 7.2 machine running nfs-ganesha proxy
> (192.168.1.9):
>
> EXPORT
> {
> Export_Id = 76;
> Path = "/export/test";
> Pseudo = "/proxy/test";
> SecType = sys;
> Access_Type = RW;
> Squash = No_Root_Squash;
> Tag = "proxy1_1";
> FSAL {
> Name = PROXY;
> }
> }
>
> PROXY
> {
> Remote_Server
> {
> Srv_Addr=192.168.1.30;
> }
> }
>
> Paritial log output from nfs-ganesha proxy at startup:
>
> main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 2.5-rc7
> load_fsal :NFS STARTUP :DEBUG :Loading FSAL PROXY with
> /usr/lib64/ganesha/libfsalproxy.so
> init_export_root :EXPORT :DEBUG :About to lookup_path for
> ExportId=76 Path=/export/test
> pxy_compoundv4_call :FSAL :DEBUG :First attempt to send XID
> 1497534513 with 148 bytes
> pxy_rpc_read_reply :FSAL :DEBUG :Recmark 80000034, xid 1497534513
> mdcache_lookup_path :INODE :DEBUG :lookup_path /export/test failed
> with Forbidden action
> init_export_root :EXPORT :CRIT :Lookup failed on path, ExportId=76
> Path=/export/test FSAL_ERROR=(Forbidden action,1)
>
> Wireshark log shows NFS4ERR_PERM on 'LOOKUP' operation (xid
> 1497534513) for 'export'.
What is the export path on the remote server (192.168.1.30)? If you mount it
directly using the kernel nfs client, can you mount 192.168.1.30:/ and see
/mnt/export? What security flavors is the remote server export using?
Frank
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
