You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> sudo systemctl status test-mount.service
○ test-mount.service - Test mount
Loaded: loaded (/etc/systemd/system/test-mount.service; enabled; preset: disabled)
Active: inactive (dead) since date
Duration: 6ms
Process: 2254 ExecStart=/bin/bash -c ls /your_pool_path/ (code=exited, status=0/SUCCESS)
Main PID: 2254 (code=exited, status=0/SUCCESS)
date <host_name> systemd[1]: Started Test mount.
date <host_name> bash[2254]: <My files>
date <host_name> systemd[1]: test-mount.service: Deactivated successfully.
Actual Behavior
I can't see my file in step 4
> sudo systemctl status test-mount.service
○ test-mount.service - Test mount
Loaded: loaded (/etc/systemd/system/test-mount.service; enabled; preset: disabled)
Active: inactive (dead) since date
Duration: 6ms
Process: 2254 ExecStart=/bin/bash -c ls /your_pool_path/ (code=exited, status=0/SUCCESS)
Main PID: 2254 (code=exited, status=0/SUCCESS)
date <host_name> systemd[1]: Started Test mount.
date <host_name> bash[2254]: <Nothing or something in /your_pool_path/ before mounted>
date <host_name> systemd[1]: test-mount.service: Deactivated successfully.
Diagnostic Logs
it can be easily reproduced.
There is a workaround: start WSL before mounting the disk to WSL.
in Repro Steps, add a step before step 1
powershell
wsl.exe-e bash -c " echo starting wsl"
This example is for demonstration only. My use case is to access files in WSL through \\wsl.localhost\Arch or Samba. If Samba is managed by systemd and I do not start WSL before mounting the disk, I will not see the files on the disk.
Although it's not a big issue....
The text was updated successfully, but these errors were encountered:
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done.
Once completed please upload the output files to this Github issue.
Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
View similar issues
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Windows Version
Microsoft Windows [Version 10.0.26100.712]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1
Distro Version
Arch
Other Software
No response
Repro Steps
test-mount
Expected Behavior
I can see my file in step 4
Actual Behavior
I can't see my file in step 4
Diagnostic Logs
it can be easily reproduced.
There is a workaround: start WSL before mounting the disk to WSL.
in
Repro Steps
, add a step before step 1powershell
This example is for demonstration only. My use case is to access files in WSL through
\\wsl.localhost\Arch
or Samba. If Samba is managed by systemd and I do not start WSL before mounting the disk, I will not see the files on the disk.Although it's not a big issue....
The text was updated successfully, but these errors were encountered: