A distributed share spreads the workload by distributing the hosting of top-level directories across FSVMs. The issue is due to the fact that Nutanix Files uses DFS namespace to provide shares to the Windows clients, meaning that the client will be connecting to the generic DFS namespace and not, in particular, the FSVM which serves the share that is which holds the VG for the share. So if the client connects to an FSVM where it just holds the re-parse point within the DFS namespace the rename operation will fail with an error of "Invalid device".
The workaround is to make sure that you connect to the FSVM serving the top level domain (TLD). Please refer to the following KB article for the detailed process to connect to the FSVM serving the TLD. Once connected to the serving FSVM the rename operation can be performed successfully.
That is not a good work around for end user. End user will not know the FSVM serving the share. Will there be a solution for that?
Trinh, thanks for the response. The issue is already fixed on Files 3.7 which is now available.
We are on Files version 3.8.1 and are experiencing the issue where when trying to rename a folder we get the “invalid device” error.
We also experience the same issue on Files 4.x