-
Notifications
You must be signed in to change notification settings - Fork 822
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
18362.53 Accessing 9P \\wsl$\xxx path sometimes fails #3995
Comments
Same problem can be recreated with cmd.exe. So .NET code not involved in PowerShell. Easy to get error about invalid address in Explorer address bar typing "\\wsl$\ubuntu" (note lowercase and no trailing '\'). Explorer displays error "\\wsl$\ubuntu" is not accessible. But once you enter it with capitalized Ubuntu it displays files and also accepts lowercase initial value (cached?) |
Started to work when in second window requested longer network path that was not yet resolved in current session "dir \\wsl$\Ubuntu\home\dainis\.ssh". Very fragile/unreliable :( |
Was able to reproduce with Powershell. Seems to be limited to getting the case of the distribution wrong. Contrast the rest of the WSL tree (say Don't read too much into what File Explorer is doing, since it does its own internal caching of paths for its own purposes, and does its own case insensitive comparisons on those paths. None of that is WSL actionable. Work around appears to be to not get the disto case wrong. |
Started to work when followed by correct-case longer path:
|
This was 18362.145 |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Please fill out the below information:
10.0.18362.53, Surface 8Gb RAM
In PowerShell 6.2 and 5.1 mix these commands in random order:
It is expected that "\\wsl$\" returns error "dir : Cannot find path '\\wsl$\' because it does not exist." (unlike Explorer which displays distro name), but correct name with uppercase Ubuntu returns list of files. Mixing complete name with incomplete many times in a row, changing capitalization for Ubuntu etc. finally will get you in state that correct path that worked before will return error. Also from other powershell window or explorer window. Then after some time it recovers.
Valid path like " \\wsl$\Ubuntu\home\dainis" will report that it does not exist. After some time work again.
Not sure whether PowerShell is somehow involved that it may cache already once resolved valid names, but I can still recreate the problem by alternating "dir \\wsl$\", "dir \\wsl$\Ubuntu", "dir \\wsl$\Ubuntu\home\dainis" in command prompt and Explorer address bar. Even after reboot.
If same command fails in one window it may work from other PS windows and it recovers problem for first window, too. I am not running the same request in parallel from two windows - strictly sequentially.
Could it be that 9P server fails and then automatically recovers?
The text was updated successfully, but these errors were encountered: