Skip to content
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

Folder from mounted windows system (NFS file system) cannot be moved to location inside the WSL (EXT4 filesystem) #1469

Closed
jepster opened this issue Dec 7, 2016 · 3 comments

Comments

@jepster
Copy link

jepster commented Dec 7, 2016

  • A brief description

If I execute

mv /mnt/c/Users/MY-USER/Dev ~/some/location/in/linux/filesystem

The bash hangs. The folder is a small one (~30 MB). If I start an new window, the cursor is not visible. I even cannot restart the computer. The "computer is being restarted" info appears and does not disappear (waited long).

  • Expected results

The "mv" program moves the folder to the desired location.

  • Actual results (with terminal output if applicable)

The entire computer cannot be restarted. No new bash window can be started.

  • Your Windows build number

14393.0

  • Steps / All commands required to reproduce the error from a brand new installation

Use the "mv" program to move a folder from a mounted windows drive from the user's home folder in the /mnt/ folder and try to move it to the user's home folder inside the WSL.

@jepster jepster changed the title Folder from mounted windows system cannot be moved to location inside the WSL Folder from mounted windows system (NFS file system) cannot be moved to location inside the WSL (EXT4 filesystem) Dec 7, 2016
@jepster
Copy link
Author

jepster commented Dec 7, 2016

Ok, I can specify the issue a bit more. It works if I specify "no" slash at the end.

This works:

mv ggg/bdhdb ggg/hihihi

This does not:

mv ggg/bdhdb/ ggg/hihihi

Somehow the slash at the end breaks the system.

@therealkenc
Copy link
Collaborator

Probably #1008

@fpqc
Copy link

fpqc commented Dec 8, 2016

@jepster This is fixed in the insider builds. It's the trailing-slash bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants