Hello Charles,
You ganesha proxy-server configuration file seems to be a bit outdated
(you can find an up to date example with this wiki link :
https://github.com/nfs-ganesha/nfs-ganesha/wiki/Testing-FSAL_PROXY )
According to your configuration this one would be correct :
EXPORT
{
# Export Id (mandatory, each EXPORT must have a unique Export_Id)
Export_Id = 12345;
# Exported path (mandatory)
Path = /nfs;
# Pseudo Path (required for NFS v4)
Pseudo = /nfspath;
# Required for access (default is None)
# Could use CLIENT blocks instead
Access_Type = RW;
Squash = no_root_squash;
# Exporting FSAL
FSAL {
Name = PROXY;
}
}
LOG {
COMPONENTS {
# ALL = FULL_DEBUG;
}
}
NFSV4 {
# GRACELESS = true;
}
PROXY {
Remote_Server {
Srv_Addr = [nfs-cems IP ADDR in XXX.XXX.XXX.XXX format];
}
}
*MANDATORY : nfs-cems must be a NFSv4.1 server .
*With the current ganesha github version, clients of FSAL_PROXY must be
NFSv4.1 client. Very recent patchs fix NFSv3 and NFSv4.0 client access
to FSAL_PROXY, soon merged in up to date "next" version of ganesha.
Regards,
Patrice
On 10/13/17 13:21, Charles Short wrote:
More complete logs with all 'errors' -
https://pastebin.com/ZzRybVeE
On 13/10/2017 11:30, Charles Short wrote:
Hi,
I am testing a v simple ganesha proxy and get pseudo mount INODE
errors on the ganesha server when I try and mount the NFS volume from
client to proxy
##On server startup
13/10/2017 10:13:43 : epoch 59e091d7 : ganesha-cems :
ganesha.nfsd-19778[main] export_display :CONFIG :M_DBG :RESULT
0xbc0e18 Export 12345 pseudo (/nfspath) with path (/nfs) and tag
((null)) perms (options=033021e2 , RWrw, ,
, , , , , sys)
### On attempted client mount -
13/10/2017 10:14:39 : epoch 59e091d7 : ganesha-cems :
ganesha.nfsd-19778[0x7facec5f3ee0] nfs4_op_lookup :NFS4 :DEBUG
:name=nfspath
13/10/2017 10:14:39 : epoch 59e091d7 : ganesha-cems :
ganesha.nfsd-19778[0x7facec5f3ee0] mdc_lookup :INODE :F_DBG :Lookup
nfspath
13/10/2017 10:14:39 : epoch 59e091d7 : ganesha-cems :
ganesha.nfsd-19778[0x7facec5f3ee0] mdc_try_get_cached :INODE :F_DBG
:Look in cache nfspath, trust content yes
13/10/2017 10:14:39 : epoch 59e091d7 : ganesha-cems :
ganesha.nfsd-19778[0x7facec5f3ee0] mdcache_avl_qp_lookup_s :INODE
:F_DBG :Lookup nfspath
13/10/2017 10:14:39 : epoch 59e091d7 : ganesha-cems :
ganesha.nfsd-19778[0x7facec5f3ee0] mdcache_avl_qp_lookup_s :INODE
:F_DBG :entry not found at j=1 (nfspath)
13/10/2017 10:14:39 : epoch 59e091d7 : ganesha-cems :
ganesha.nfsd-19778[0x7facec5f3ee0] mdc_try_get_cached :INODE :F_DBG
:mdcache_avl_qp_lookup_s nfspath failed trust negative no
The whole setup including build config files and logs is here
https://pastebin.com/DEnER83J
What am I doing wrong?
Thanks
Charles
------------------------------------------------------------------------------
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
--
Patrice LUCAS
Ingenieur-Chercheur, CEA-DAM/DSSI/SISR/LA2S
tel : +33 (0)1 69 26 47 86
e-mail : patrice.lu...@cea.fr
------------------------------------------------------------------------------
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
