WSL: mv hangs
Please use the following bug reporting template to help produce actionable and reproducible issues:
- A brief description
After issuing mv x86_64-pc-linux-gnu-library/ x86_64-pc-linux-gnu-library2 from the command line, it hangs.
What is more, even after I closes the Bash window, I cannot start a new one normally: the new one just shows nothing.
- Expected results
Does the job very quickly and ends.
- Actual results (with terminal output if applicable)
Nothings. Even Ctrl + C cannot kill it.
- Your Windows build number
14393.10
- Steps / commands required to reproduce the error
- Strace of the failing command
- Required packages and commands to install
See our contributing instructions for assistance.
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Reactions: 4
- Comments: 17 (6 by maintainers)
This has been fixed and the fix will be available once we start Windows Insider flighting,
@onomatopellan The bug manifests as a deadlock in our driver (recursive lock acquire) so unfortunately the only way out is to reboot.
Closing this out as it’s a dupe of #671
How is a kernel deadlock not worthy of an update to Anniversary, ie “release build”?
I’m running into this problem too, with mv hanging. I’m running 10.0.14393.
@forresthopkinsa - Thanks for confirming. I’m currently working with the servicing team to see about backporting this fix as a Windows Update.
I can’t wait for this “Creators” update… I have just had to reboot windows 3 times in the last half hour because it’s impossible to remember that such a horrible bug exists!
Probably related to https://github.com/Microsoft/BashOnWindows/issues/650. When a path ends with slash problem happens. It’s already fixed but the fix didn’t make it to Anniversary Update.
these should work mv x86_64-pc-linux-gnu-library x86_64-pc-linux-gnu-library2 mv x86_64-pc-linux-gnu-library x86_64-pc-linux-gnu-library2/
EDIT: I have reproduced your problem and now even closing bash and disabling LXSS service there is a MV picoprocess on task manager and I can’t run bash anymore. I can’t kill the process so I guess I’ll have to restart Windows. Ugh.
@Armel2017 – thanks for reporting.
git mvis actually different in relevant ways than regularmv. Specifically, there are large known slowdowns with git operations in some cases that occur because of git’s history tracking, and which therefore don’t affect regular filesystem commands.Do you see this with regular
mvas well? If not, could you please file a new ticket with more information about how to reproduce the issue that you are seeing? Specifically, in addition to your Windows build (from above), also whether you’re seeing this in VolFS (/home, etc) or DrvFS (/mnt), and a link to an affected git repository if it is public.I believe this was fixed a while ago in Insider builds. Insider builds have a lot of major WSL fixes and improvements at this point.
If you can’t or don’t want to run an Insider build, WSL fixes in Insider builds are not being backported to existing stable Windows releases, but they will be in the next major stable Windows release (the “Creators” update). I don’t think the release date has been publicized, but if you look around online, you’ll find many rumors that it’s a couple months away from release.
Any progress on this? It quite limits the ability to build anything on the linux subsystem, as one of the autoconf checks if to see if “mv dir1/ dir2” works…