New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: Can't create top level directories with a uuid UNC path #3864
Comments
What do you think rclone should be doing differently here? I'm not an expert on Windows file systems so I'm not sure what the best fix is? Or is it just document the quirk and move on? |
Document and move on. Probably something to do with curly braces in a UNC path. |
It is strange it only doesn't work at the root. This is almost certainly a go runtime bug - I looked at the go issues and there are lots about mkdir not working properly on Windows at the root, however they were all closed so this is probably a new issue. I'll leave this issue open for someone else to find if they are affected by it. |
@iseahound - did you want to try on the later version and beta and see if it still exists? If it was a go issue, it might have been solved. |
Still failing on v1.51.0-353-g5f71d186-beta. |
I think what we need to do is write a small go program to demonstrate the problem and post it as an issue on the go bug tracker. I don't have a Windows machine to hand right now - @iseahound is that something you could help with? |
Let's reproduce and document it as Windows Caveat. |
@albertony |
I made an upstream bug about this on Go: golang/go#39785 |
This was documented recently |
Hey Nick,
Windows has a lot of specific quirks, and this is another one of them 馃檨.
This one is really minor (and only affects top level directories).
Using a uuid instead of a drive letter introduces an error only when creating top level directories.
Here's a short script demonstrating the bug:
To get the uuid value for the volume run
mountvol
and copy and paste your unique value into the script.Note that using a regular UNC path like
\\?\C:\
works fine.The text was updated successfully, but these errors were encountered: