[NFS-Ganesha-Devel] Re：Re: Invalid device when renaming folder with windows nfs client

We have the following requirements: 1. windows nfs client mount with /gv0 2. linux nfsv3 mount with / 3. linux nfsv4 mount with /, other than /gv0 ----- 原始邮件 ----- 发件人："Frank Filz" <ffilzlnx(a)mindspring.com&gt; 收件人：&lt;zhbingyin(a)sina.com&gt;, "'ganesha-devel'" <devel(a)lists.nfs-ganesha.org&gt; 主题：[NFS-Ganesha-Devel] Re: Invalid device when renaming folder with windows nfs client 日期：2019年07月02日 01点27分 The Windows client may not be expecting an export to actually be “/”. Why do you want the export at “/” for NFSv4? Frank From: QR [mailto:zhbingyin@sina.com] Sent: Monday, July 1, 2019 3:31 AM To: ganesha-devel <devel(a)lists.nfs-ganesha.org&gt; Subject: [NFS-Ganesha-Devel] Invalid device when renaming folder with windows nfs client In windows nfs client, rename fails with "Invalid device" when Mount_Path_Pseudo is true, but if set Mount_Path_Pseudo to false rename succeeds.Is anyone know about this?Thanks in advance. Ganesha server info ganesha version: V2.7.4 FSAL : glusternfs client info nfs version : nfs v3 client info : windows 7 Ganesha config infoNFS_CORE_PARAM { Mount_Path_Pseudo = false;}EXPORT{ Export_Id = 1; Path = /gv0; Pseudo = /; Protocols = 3,4; Access_Type = RW; Squash = No_root_squash; Sectype = sys,krb5,krb5i,krb5p; # Exporting FSAL FSAL { Name = GLUSTER; Hostname = x.y.z.x; volume = gv0; }} _______________________________________________ Devel mailing list -- devel(a)lists.nfs-ganesha.org To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org