-
Notifications
You must be signed in to change notification settings - Fork 827
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
There are always empty folders like wslxxx in my wsl root directory. #10690
Comments
same as you: WSL Version: 2.0.4.0 |
Thanky ou @aihao2000. Can you share /logs of a repro (start the logs when the wsl* folder doesn't exist, reproduce the issue where it's created, and stop log collection ? ) |
here is my log: |
@OneBlue Can the above log be used to troubleshoot the problem? The problem I created with wslxxx does not occur very frequently, and it may take a long time to reproduce. |
@OneBlue Another person seems to have the same bug as me. He recorded the log and provided it. Is there any way to troubleshoot the problem? |
I have the same problem, using wsl2 |
Unfortunately I'm not seeing anything in the logs they shared. Just checking, if you delete all the |
@OneBlue No, maybe need to see for a while, folders latest updated is Aug 30 |
@OneBlue wsk* can be deleted, but requires root privileges |
Same issue here as well |
I reproduced this problem. After running |
Windows Version
Microsoft Windows [Version10.0.22621.2428]
WSL Version
WSL 版本: 1.2.5.0 内核版本: 5.15.90.1 WSLg 版本: 1.0.51 MSRDC 版本: 1.2.3770 Direct3D 版本: 1.608.2-61064218 DXCore 版本: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows 版本: 10.0.22621.2428
Are you using WSL 1 or WSL 2?
Kernel Version
默认分发: Ubuntu 默认版本: 2
Distro Version
Release: 22.04
Other Software
No response
Repro Steps
Empty folders such as wslxxx always appear automatically in my wsl root directory. I don't know how it is triggered and why it occurs.
Expected Behavior
No inexplicable files such as wslxxx appear
Actual Behavior
Every once in a while, many empty folders of wslxxx will appear.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: