search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.48k stars 822 forks source link

Frequent Lag and TCP RST Responses with NFS Server on WSL2 Debian 12 #12233

Closed shangwei2016 closed 1 week ago

shangwei2016 commented 2 weeks ago

Windows Version

10.0.22631.4317

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.153.1-2

Distro Version

Debian 12

Other Software

The NFS client is running on ARMv7-A development boards with a kernel version of 4.19. One board is from Rockchip, and the other is from MediaTek, both exhibiting the same behavior. Therefore, I believe it would be a good idea to first try using a Linux NFS client.

Repro Steps

  1. Install NFS Server on WSL2, Debian 12 1.1 sudo apt install nfs-common nfs-kernel-server rpcbind 1.2 sudo mkdir /nfs 1.3 sudo chown nobody:nogroup /nfs 1.4 sudo chmod 777 /nfs 1.5 Append '/mnt/nfs *(rw,sync,no_root_squash,no_subtree_check)' to /etc/exports 1.6 sudo /etc/init.d/nfs-kernel-server restart 1.7 sudo service rpcbind start

  2. Execute commands on my development board 2.1 mount -t nfs -o nolock 192.168.7.21:/nfs /nfsroot 2.2 cd /nfsroot, if I operate files in this directory, such as the ls command, there is often a 3-second delay.

Expected Behavior

I expect file operations in the mounted directory to run smoothly and seamlessly, without frequent freezes or delays.

Actual Behavior

If I operate files in this mounted directory, such as the ls command, there is often a 3-second delay.

Diagnostic Logs

No response

github-actions[bot] commented 2 weeks ago

Logs are required for review from WSL team

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

microsoft-github-policy-service[bot] commented 1 week ago

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!