6:23 p.m.
Back in April I wrote:
On Thu, 9 Apr 2020, Pfaff, Todd wrote:
> I'm having stability problems with nfs-ganesha 2.8 and PROXY FSAL on
> CentOS 7.
and this has been ongoing for me since then. Today I finally stumbled onto
something that may have solved at least some of the problems that I've been
having with nfs-ganesha. I also posted the following as a follow up to the nfs-
ganesha github issue: frequent failures with PROXY FSAL (#580).
...
I've discovered something that may be relevant to this issue.
- My nfs-ganesha server is serving several EXPORTs.
- Two of these EXPORTs refer to identically named PATHs on two different
back-end servers.
- I've now changed these so that the back-end server paths are different.
- I've tested this multiple times with multiple VMs and it appears that
this change may have eliminated all traces of the problems that I've
been describing here.
Does this make sense? Is it known that nfs-ganesha can not have multiple
exports with the same value for the Path?
I'm not that familiar with FSAL_PROXY, and I'm not sure how it handles multiple
exports. That is actually an area that needs more testing and more resolution.
Do you use
NFS_CORE_PARAM { mount_path_pseudo = true; }
You may be running into issues if path is the same with NFS v3 clients.
If that isn't the issue, we do need to make the proxy support more robust because
certainly we should allow multiple back end servers exporting the same path.
Frank