Copy command fails on azure file shares with force=true, because stat(...).inode == 0

[jonbarkerlondon]

I created a SO question, but received no further info.

https://stackoverflow.com/questions/63002995/julia-copy-method-on-azure-fileshares-fails-stat-inode-is-always-zero

---

When copying data from \azurefileshare\a\1 to \azurefileshare\a\2 we get an error:

'src' and 'dst' refer to the same file/dir

After some investigation, it seems julia uses the stat command to determine if folders are identical by comparing the stat(xxx).inode and stat(xxx).device

However, the inode is always 0 for any Azure folders that we pass into stat(foldername).

Questions:

Have we misconfigured our Azure file shares?
Is this a bug in the stat() implementation in julia?
Is the julia inode comparison logic flawed?
Much appreciated.

[StefanKarpinski]

Julia uses libuv for the stat implementation, so if there is a bug with it, it's an upstream libuv bug. I wonder if an inode of zero occurs in normal cases. If not, then we could use that to detect that something different needs to be done. But it would be even better if the inode was correctly reported.

[StefanKarpinski]

Also asked at https://stackoverflow.com/questions/63002995/julia-copy-method-on-azure-fileshares-fails-stat-inode-is-always-zero