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; }}
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@lists.nfs-ganesha.org> 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 : gluster nfs client info nfs version : nfs v3 client info : windows 7 Ganesha config info NFS_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; } }
participants (2)
-
Frank Filz -
QR