ihoukai
ihoukai
@boulos i tried nfs-ganesha V4-dev.44，the problem still exists； the client directly connects to the NFSD backend is fine. The log is below: [nfs-ganesha-log.tar.gz](https://github.com/nfs-ganesha/nfs-ganesha/files/5682376/nfs-ganesha-log.tar.gz)
@boulos nfs-ganesha V4-dev.44 PROXY_V3 is fine，PROXY_V4 has problem
@boulos I uploaded nfs-ganesha V4-dev.44 PROXY_V4 logs and nfsd logs [nfs-ganesha-v4-log.tar.gz](https://github.com/nfs-ganesha/nfs-ganesha/files/5686202/nfs-ganesha-v4-log.tar.gz) [nfsd-log.tar.gz](https://github.com/nfs-ganesha/nfs-ganesha/files/5686203/nfsd-log.tar.gz)
@boulos Any progress? What can I do for you?
@boulos i need NFS v4.1 to my backend，Using Proxy V3 to install our K8S cluster, we found that Proxy V3 had file lock-related problems, causing the startup failure of Mariadb...
@boulos yes, i have statd 
@boulos backend has rpc.statd 